Last post Jan 25, 2008 09:15 PM by johnnystock
Jan 25, 2008 06:43 PM|johnnystock|LINK
specific ID added to the selected row.
In the previous release of our application this worked fine. In the release we are working on currently there have been significant changes to the overall application such as the addition of a Master Page, themes and a complete css redesign. In the process
the scrolling functionality has been broken in IE (still works in firefox) although there is no script error. Through testing I can say that IE does find the added span and executes the method which executes without error but no longer scrolls. As I said,
it works fine in Firefox which makes it even more frustrating as the app is IE only.
Does anyone have any thoughts? Could there be a style element on a parent object that is interfering with that method?
Jan 25, 2008 08:19 PM|JoshStodola|LINK
As of right now, this is nothing but a guessing game. You should post some relevant code!
What I would do to debug this, is to examine the rendered markup (run the site, and then view the source) of the page that works, and the page that doesn't work. Examine them both, looking for structural differences. If the markup is identical, the next
Jan 25, 2008 08:33 PM|johnnystock|LINK
Thanks for the input but I've been doing what you suggest for many hours and have not found anything that stands out. I was hoping that someone had experience with this exact issue and might know of a possible css element that would do this. As I stated
the entire CSS structure of the application has changed this phase so digging through 2200+ (that's not a typo) lines of css was something I was hoping to avoid.
Jan 25, 2008 08:46 PM|JoshStodola|LINK
Since you refuse to post any code or screenshots of the issue, I will just take a shot in the dark...
Add overflow-y:scroll; in the CSS for the <div> that needs to scroll.
Jan 25, 2008 08:52 PM|JoshStodola|LINK
var div = document.getElementById('YOUR_DIV');
div.scrollTop = div.getElementById('OBJECT_TO_SCROLL_TO').scrollHeight;
Jan 25, 2008 08:59 PM|johnnystock|LINK
That just might do it. I'm also thinking it may be related to where the script executes in the page lifecycle now. Since they added master pages this script might get kicked off before the page is done rendering, which of course would make it fail. I'm
testing that theory now.
Jan 25, 2008 09:10 PM|JoshStodola|LINK
It would make it fail, but then you would see a script error. Didn't you mention that there were no script errors? You can enable the debugger in IE through the Advanced options to get an alert in your face for each script error (that way there is no way
you could miss it!).
of the page in Firefox...?
Jan 25, 2008 09:15 PM|johnnystock|LINK
hard refreshes just in case). As far as Master pages changing IDs you are right but also that would throw a script error if it didn't find it.
I'm still playing with CSS, it's got to be in there somewhere.