Alan Gresley wrote: > Gunlaug_Sørtun wrote: >> <http://tjkdesign.com/test/ie8/links.asp> > > > That the same issue as I'm having with my menu. > > <http://css-class.com/articles/ursidae/bears5ddh-kbaccess.htm> > > It is similar as with IE6 requiring hasLayout and display:block on > anchors to make the whole anchor area click-able. This is not > happening with my other menus. Even my new templates navigation > anchors are showing ok. I don't think this is a stacking error as per > se but due to something deeper.
If a browser can't stack various layers of one element together in the right order on top of all layers of another element, without explicitly being "told" to group and stack element layers by using a nonsensical property/value for the case, then it is a serious stacking bug. >>> Parsing of the non-valid import filters is fixed. >>> >>> <http://css-class.com/test/css/selectors/ie/import-hacks.htm> >>> >>> Goerg, you use this filter don't you :-) >> Yes, so I shouldn't have to worry about IE8 picking up IE7 styles. >> How does it handle that filter if rolled back to IE7 ? > > > I don't understand what you mean by "How does it handle that filter > if rolled back to IE7?" I see that my band pass filter works. Toggle IE8 to render like IE7, and see how it handles such filters that are known to work in a certain way in IE7. > Sorry Georg, but you are using a xml prolog like myself, and this is > throwing IE8 into quirks mode. > > http://css-class.com/test/css/selectors/ie7hacktargetingopera4.htm Should *not* happen, so if true that counts as a *serious bug* in IE8. Sounds like IE8' mode switching is totally corrupted in this beta, and on top of that it doesn't act *identical to* the earlier versions it is said to emulate either. All in all a "good" recipe for breaking large parts of the web. >> BTW: how does IE8 beta1 handle all these @import hacks... >> >> <http://www.gunlaug.no/contents/wd_chaos_20.html> > > > IE8 now parses them correctly. Some good news. Again, toggle back to IE7 and test again. If IE8 doesn't emulate previous versions/modes *identical to* those previous versions/modes, the whole version target mess that has been "the talk of the town" lately, becomes "utter nonsense" in any order. >> ....not to mention these... >> >> <http://www.gunlaug.no/contents/wd_chaos_27.html> >> <http://www.gunlaug.no/contents/wd_chaos_28.html> > > > The line is yellow in both, IE8 fails. A "less-important failure", but a failure never the less. If left unfixed it opens up IE8 for "the ugliest IE-hack ever invented", and breaks with what the W3C standard says: "HTML allows authors to associate any number of external style sheets with a document."[1]. Clearly IE/win doesn't allow all that much, while other major browsers allow /almost/ any number - if given enough time and resources to handle them. regards Georg [1]http://www.w3.org/TR/html401/present/styles.html#h-14.3.1 -- http://www.gunlaug.no ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
