Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!us.feeder.erje.net!newsfeed.straub-nv.de!news-1.dfn.de!news.dfn.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: "Mel Smith" <med_cutout_syntel@aol.com>
Newsgroups: comp.lang.javascript
Subject: Re: IE8 attachEvent problem
Date: Mon, 21 Jan 2013 09:52:38 -0700
Lines: 49
Message-ID: <am5a2tF758fU1@mid.individual.net>
References: <am2ojqFk54hU1@mid.individual.net> <50fc2fac$0$6566$9b4e6d93@newsspool4.arcor-online.net> <am2pjiFkcl1U1@mid.individual.net> <am2r29Fko0fU1@mid.individual.net> <50fd2118$0$6563$9b4e6d93@newsspool4.arcor-online.net>
X-Trace: individual.net VqZQocUoGXBvCd9u9hluDwocDZF87NSXrtiEPpW1t/9jr80IUneLwZ6Ybljfhe4VeC
Cancel-Lock: sha1:kxRv70CFkkfQXHmsHuVsew5dPVM=
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
X-RFC2646: Format=Flowed; Response
Xref: csiph.com comp.lang.javascript:18189

Martin said:

"Martin Honnen" <mahotrash@yahoo.de> wrote in message 
news:50fd2118$0$6563$9b4e6d93@newsspool4.arcor-online.net...
> Mel Smith wrote:
>
>>      It *does this* but still shows the error on IE8.
>
>
> I am not sure about older IE versions, according to 
> http://msdn.microsoft.com/en-us/library/ie/ms536730%28v=vs.85%29.aspx 
> scrollIntoView takes a boolean argument.
> Does the error vanish when you explicitly call
>    document.getElementById(tid).scrollIntoView(true);
> ? Or which statement currently gives the error?
>

Hi Martin:

    In a 'later/lower' post, I corrected statement in question and used 
'document.body. etcetera' .  This stopped the error.

    With that correction, I now have the following results:

    IE8 - Works corectly
    FF -   Works correctly
    Opera - Works correctly
    Chrome - Page displays at *top*, not where it was 'remembered'
    Safari - Page displays at *top*, not where it was 'remembered'

    Since my users are older retired north americans, and since in this 
demographic (IE and Chrome) are predominant,  I'd like to determine why 
Chrome is not scrolling to the remembered position (which is a multi-line 
cell in a long 3-column table)

    btw,  I *did* place a 'true' as an argument in the scrollIntoView() 
function.  But, this is the default anyway and made no difference.

    Also, I placed an Alert() just ahead of the 'scroll' code to ensure that 
the ID was correct. It _was_

    So, if I change the 'onload' event to point at my new ID, why is it 
ignored by Chrome and Safari when I 'return' to the page ??

Thanks for the comment.

-Mel Smith