Comments

1. Igo AtM on February 27, 2006 at 12:46 pm said:

   3 dayzz of climbing up the wall and it may have been 3 months without the above tip. Client now removed from ceiling and nail marks plastered over. Fellow seekers will be pointed this way
   Many Many Thanks
2. Kae Verens on February 27, 2006 at 1:59 pm said:

   lol! nice to see that I am indirectly saving clients from the wrath of frustrated web developers.
3. Bikeman on March 22, 2006 at 2:59 pm said:

   Why is it a problem to be 30? That sort of crap has resulted in IT professionals increasingly being unemployable well before middle age. What you sow you will reap.
4. Kae Verens on March 22, 2006 at 3:05 pm said:

   what? I think you misread my quote. I did not say that 30 was the age at which web developers suddenly forget how to code. It was merely a humourous reminder to myself that I am getting “old” (whatever that means, these days).
5. Ryan on April 14, 2006 at 8:37 pm said:

   Thanks for the investigative work. I’m being bit by this.
6. Ruud on May 12, 2006 at 11:26 am said:

   Another workaround might be to set the z-index of all relative elements dynamicly when building the page. First element gets z-index 10000 or so, second gets 9990 and so on. A bit of a dirty trick, but if this can be achieved server side, at least you wont bother the client with it.
7. Kae Verens on May 12, 2006 at 7:47 pm said:

   That’s an interesting idea, Ruud – must try that out. If it works, I’ll suggest it for the IE7 script project (all IE bug workarounds should probably be pointed out there).
8. Michael on May 18, 2006 at 1:43 pm said:

   You should set the z-index on the position:relative elements (and not on the absolute elements within it if you have any).

   Also note that when setting the z-index for a positioned element, a new z-order stack will be created for the child elements.
9. Y-coci on May 29, 2006 at 9:05 am said:

   Micheal,

   This seem to work.

   thanks much!!!
10. Y-coci on May 29, 2006 at 9:06 am said:

    Michael,

    This seem to work.

    thanks much!!!
11. Mari on January 6, 2007 at 10:45 pm said:

    Michael, thank You for the exellent tip =)
12. tomchito on July 14, 2007 at 9:24 pm said:

    Thx 4 the tip. I hate IE but my page has to work with this ‘browser’.
13. Rengirl on August 3, 2007 at 2:24 am said:

    THANK YOU THANK YOU THANK YOU! I was splitting hairs over this stupid IE css error and I was about to give up until I found this. Problem solved.
14. Jens Brandt on January 3, 2008 at 4:42 pm said:

    Let me join the choir of thankful people: I’ve been looking around the web, but this sentence explained it all: “It appears that if you have multiple position:relative elements in your code, then IE sets up separate Z layer contexts for each one, which ignore each other”.
    Thanks!
15. eric mueller on January 12, 2008 at 8:11 am said:

    thanks for this info — my easy workaround was to just wrap my elements in another div, positioned absolutely… i.e.

    <- this is to fix bug

    etc etc

    <– close ie7 fix div

    thx thx
    E
16. eric on January 12, 2008 at 8:19 am said:

    eh, ignore that fix. the code didn’t come across anyhow!
17. BugRocker on January 18, 2008 at 11:37 am said:

    Go an easier workaround:

    z-index: 0 !important; z-index: -1;

    Et Voila!