Gunlaug Sørtun wrote:

> 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.


I know the fix/bug. As I said previously this is deeper. I did have this.

div#navwrap {
        width:9em;
        margin-left:1.2em;
        /*position:absolute;
        top:80px;
        left:0;*/
        float:left;
        margin-bottom:30px;
}

And if I positioned the navigation wrapper instead of float it.

div#navwrap {
        width:9em;
        margin-left:1.2em;
        position:absolute;
        top:80px;
        left:0;
        /*float:left;*/
        margin-bottom:30px;
}


hey presto, I can hover the whole block of the 1st generation anchors. The bug 
was never effecting any other generation of anchors. I still don't know if this 
is a stacking issue (Ingo, where are you?) but floating and positioning shows 
two different results. The former only shows the hover over the text node where 
the later shows the hover over the whole block. Here is the same menu now 
positioned instead of floated.

http://css-class.com/articles/ursidae/bears5ddh-kbaccess-ie8.htm


> > 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, remember that Ingo had to help me find that hidden blue arrow 
after I had replied to you. I didn't know what you meant. :-)


 
> > 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.


I not completely correct here in a true sense since this can only happen when a 
comment appears between the xml prolog and doctype.

<?xml version="1.0" encoding="utf-8"?>

<!-- this comment will trigger quirks mode in IE8 -->

<!DOCTYPE>



> 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.
[...]
> 
> regards
>       Georg
> -- 
> http://www.gunlaug.no


I haven't tested your imports yet but IE8 in IE7 mode seems different from the 
true IE7. I can't test personally now since I don't have IE7 anymore but if my 
memory serve me correct, things have changed.

http://css-class.com/test/css/visformatting/floats-with-block-elements.htm

Test 2 display:block is now different. The block is now sitting out to the 
right of the first float instead of sitting to the left underneath both floats.

Test 4 display:table is now different. The block is now sitting out to the 
right instead of sitting to the left underneath both floats. This should be 
like this since IE7 doesn't support display:table. The same applies to Test 6 
display:run-in, not supported by IE7.

Can someone with a virtual PC confirm this please? Can some also confirm my 
passes and fails? I believe that only Gecko 1.9 is showing the correct behavior 
and layering.

It seems both mode are out of whack.


Alan

http://css-class.com/


______________________________________________________________________
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/

Reply via email to