S
steve.toub
Hi--
I maintain a website and one of my users complains that when viewing
some large HTML pages (roughly 1MB), the scrolling is slow and jerky.
I am able to duplicate this using IE 6 (WinXP SP2 with all patches
applied), regardless of the scrolling technique (click on scrollbar,
page down, spacebar). Scrolling is fine in the following cases:
* in all other applications besides IE
* on smaller sizes HTML pages in IE (this site and others)
* in Firefox 1.5 for this same set of pages that render poorly in IE
The HTML on these pages is completely valid. There are no <table>s on
the page. An example is:
http://www.cdlib.org/inside/resources/updates/ucsb20060117.html
I have turned smooth scrolling on and off, installed the latest video
drivers, and the problem persists.
I did some searching but I haven't seen anything in the Microsoft KB,
Usenet, or Google that addresses this. Does anyone have any ideas on
how to resolve this? I know I can workaround by dividing this page into
smaller pages or by asking users to use Firefox, but I'm hoping to
avoid those workarounds.
--SET
I maintain a website and one of my users complains that when viewing
some large HTML pages (roughly 1MB), the scrolling is slow and jerky.
I am able to duplicate this using IE 6 (WinXP SP2 with all patches
applied), regardless of the scrolling technique (click on scrollbar,
page down, spacebar). Scrolling is fine in the following cases:
* in all other applications besides IE
* on smaller sizes HTML pages in IE (this site and others)
* in Firefox 1.5 for this same set of pages that render poorly in IE
The HTML on these pages is completely valid. There are no <table>s on
the page. An example is:
http://www.cdlib.org/inside/resources/updates/ucsb20060117.html
I have turned smooth scrolling on and off, installed the latest video
drivers, and the problem persists.
I did some searching but I haven't seen anything in the Microsoft KB,
Usenet, or Google that addresses this. Does anyone have any ideas on
how to resolve this? I know I can workaround by dividing this page into
smaller pages or by asking users to use Firefox, but I'm hoping to
avoid those workarounds.
--SET