Lyn Patterson wrote:
"stacking bugs" ? something for me to research.
You'll find few references to that bug under that "name". It's rather a
description of how the bug works - individual layers of an element get
wrongly stacked relative to individual layers of other elements
_visually_ in the same area.
Search for "hasLayout" related bugs instead, and look for bugs that
sometimes - *but not always* - can be fixed by adding 'hasLayout'
triggers. There you may find the fix: 'position: relative' on the
element itself and/or on related elements in combinations with or as
alternative for 'hasLayout' triggers, and can deduct what's really going
on from there.
FYI: IE7 has several new versions of these "stacking bugs", since all
they have done in IE7 is to _patch over_ the most documented and "talked
about" occurrences of bugs found in IE6. In doing so they have just
"moved the old bugs around" - especially the "stacking bugs",
without fixing more than an insignificant number of bugs for real.
In case you're not familiar with stacking of element-layers and
generation of anonymous boxes and such: browsers have to split all
elements into individual layers and add characteristics to each of them,
and then stack them all at the correct levels for visual appearance.
This is part of what makes rendering in browsers a bit more complex than
most web designers like to think, and needless to say that IE/win (any
version) isn't particularly good at this splitting and subsequent stacking.
regards
Georg
--
http://www.gunlaug.no
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
