Topic: overflow: auto bug in IE5 for Mac (Page 1 of 1)

When using overflow: auto for an element inside a page, the page nonetheless becomes long enough to contain the entire content of the element, even though part of it is hidden. This causes your page to scroll down as far as where the hidden content goes. This is a known bug in IE5 for Mac and very annoying to me. Has anyone found a workaround???

an example of this bug is
http://www.xs4all.nl/%7Eppk/js/ie5mac/auto.html

F.Y.I if anyone is ever researching this bug.

No one has been able to provide a direct workaround to this problem. What you can do instead is create a different page and use an iframe instead of a div layer. iframes display perfectly in IE5 though they can be fussy and not totally supported in other browsers.

Then on your original page you just add a javascript to automatically redirect any Mac IE5.0 to the other page with the iframe. The javascript could be something like this

<script language="JavaScript">
if(navigator.appVersion.indexOf("MSIE 5.")!=(-1)
&& navigator.appVersion.indexOf("Macintosh")!=(-1)) {
top.location.href = "new-iframe-page.html";
}
</script>


Good luck.




[This message has been edited by kelly001 (edited 01-20-2003).]

Hmm. Sounds obnoxious.

Perhaps setting the "clip" property for the div or a higher-level element (such as the body) and setting overflow:none for *that* element will prevent the problem?

I think I vaguely remember something like this, not sure though...

no, setting the clip property or changing overflow to a different value will not resolve the problem without affecting an other aspect of your page. It is a well documented browser bug from what I've been able to gather on the net and no one has offered an easy fix to this. This is still the most functional fix I've been recommended to work around this. Then again, you are doing all this only to satisfy Mac users under IE5 (maybe 5% of your users if that), it's maybe not crucial to every webmaster out there to go through this.

If ever you find an easier workaround, please post back here! thanks!

MacEdition's CodeBitch identifies it as a bug. Read more here.