 |
|
We are providing HierMenus to you at no cost. HierMenus code requires a confirmed membership with internet.com. Please register by clicking here and come back soon to download your free copy of HeirMenus code.
|
|
 |
|
 |
 |
|
home / issues / issue #2
| Issue: | Frequent Image Rollovers Cause
Browser to Stop Responding |
| Browser: | Internet Explorer 5/5.5/6 |
| Platform: | Windows |
| Description: | In Internet Explorer, rolling
repeatedly and quickly over rollover images (i.e., images which change each
time the mouse rolls over them) can cause the browser to stop responding to
further local downloads (i.e., more images or new pages from the same server).
The page itself remains visible, and
the back buttons of the browser will typically work. But the user will be unable
to click through to any further pages within the same domain. Pages from external domains will be retrievable. In HM this error
can be triggered naturally with the use of "more" image rollovers. |
| Cause: | The cause is connection related, and
Microsoft has confirmed this behavior to be a bug as described in this knowledgebase article:
BUG: Internet Explorer Stops Responding When You Download Images
We've only been able to replicate the problem in HM when the Internet
Explorer cache setting is set to check for new versions on "Every Visit to the Page," however, some users
of customized Internet Explorer versions have noted that they can even receive the
error when the cache settings are set to "automatically." (Could the cache setting
displayed in Internet Options be different from the registry setting used for
cache purposes? See this Microsoft
Knowledge Base Entry for registry setting details.) |
| Comments: | Though not specifically HM
related (we are able to trigger the error via even simple rollover examples,
such as this one), HM can trigger this
error via its use of more image rollovers. Possible workarounds, therefore,
all involve reducing or eliminating the more image rollovers in your design:
- Have users change their cache settings to "Automatically."
- Do not use image rollovers; i.e., specifically set ImageSrcOver
and ImageSrcLeftOver to null. The initial
more images will still be displayed in this scenario; they simply won't
change color when the user rolls over menu items.
- Turn off more images completely via the
MoreImagesVisible
configuration parameter.
Note that when the error occurs, there is typically an accompanying memory
usage spike in the browser. We do not know if the memory spike causes the
error or the error causes the memory spike. Because of this, some users have
incorrectly reported this issue as an IE memory leak. A memory leak,
however, results in the loss of memory when moving from page to page; this
error can be triggered entirely within a single page.
Any additional information on this issue would be appreciated. If you have any
further information or other workarounds please feel free to share them:
IE Rollovers
|
| Posted: | April 24, 2003 |
|
|
