Results 1 to 8 of 8

Thread: Chrome Menu "Z-Index" not always on top

  1. #1
    Join Date
    Jun 2006
    Posts
    2
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Question Chrome Menu "Z-Index" not always on top

    Admittedly, I've modified the chrome menu's appearance but hopefully I'm not responsible for the anomaly. The drop down menu doesn't cover drop down list boxes. I've experimented with position: absolute and z-index: but I can't resolve the problem.

    Example:
    http://gowebsite.com/domain_appraisals.html
    css: http://gowebsite.com/chrometheme/chromestyle3.css
    menu html: http://gowebsite.com/menu.html

    Expand "Quick Domain Search" on the right hand side. The right side drop down menus don't cover the drop down box below.

  2. #2
    Join Date
    Mar 2006
    Location
    Illinois, USA
    Posts
    12,164
    Thanks
    265
    Thanked 690 Times in 678 Posts

    Default

    Dropdowns are likely just placed on top of everything. Don't you want to be able to see them when they drop down?

    Maybe some complex css will be able to override this, but, really, why?

    I'm sure someone else will know the technical reasons/settings for this, but I do think it's just a browser default. It would be somewhat like having something over the file menu... just seems like it should always be on top.
    Daniel - Freelance Web Design | <?php?> | <html>| español | Deutsch | italiano | português | català | un peu de français | some knowledge of several other languages: I can sometimes help translate here on DD | Linguistics Forum

  3. #3
    Join Date
    Jun 2006
    Posts
    2
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    I made it difficult to see the specific situation I was talking about so here's another try:
    http://www.gowebsite.com/chrometheme/menuz.gif

    The dropdown list box in the content that lives below the drop down menu pops through the menu.

    Version 2 of chrome menu appears to be doing the same thing:

    http://www.gowebsite.com/menu_test.html

  4. #4
    Join Date
    Oct 2006
    Posts
    2
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    This happens because IE cheats and uses the operating system to render those drop down menus after the page is loaded instead of using the browser. I think it saves memory or loads the page faster or something like that. I bet you don't get that problem with firefox. Might be fixed in IE7, I wouldn't know I just use Linux

  5. #5
    Join Date
    Aug 2004
    Posts
    10,143
    Thanks
    3
    Thanked 1,008 Times in 993 Posts
    Blog Entries
    16

    Default

    I'll get to updating the Chrome Menu script soon with the ability to actually hide a form object when the menu drops down, similar to in Drop Down Tab menu.

  6. #6
    Join Date
    Sep 2005
    Posts
    882
    Thanks
    0
    Thanked 3 Times in 3 Posts

    Default

    Quote Originally Posted by ddadmin
    I'll get to updating the Chrome Menu script soon with the ability to actually hide a form object when the menu drops down, similar to in Drop Down Tab menu.
    That is really the bad option here.The problem is caused by a design decision in IE 6 or less(http://msdn.microsoft.com/library/de...cts/select.asp).Select elements are windowed controls. This means they only obey z-index compared to other windowed controls. Windowless controls obey the z-index of other windowless controls. Luckily, an iframe is both a windowed and windowless control. So you insert an iframe in between the flyout menu and the select menu. Then use IE's opacity filter to hide the iframe. Then use conditional comments(if lse IE 6) to run this extra code. This is normally called the "iframe shim". A google search will probably provide more info.

  7. #7
    Join Date
    Aug 2004
    Posts
    10,143
    Thanks
    3
    Thanked 1,008 Times in 993 Posts
    Blog Entries
    16

    Default

    Blm126:
    Interesting, this is the first time I've heard of the iframe shim technique. I'll read up on it, though I think any solution is only interim anyway as IE7 addresses the issue.

  8. #8
    Join Date
    Sep 2005
    Posts
    882
    Thanks
    0
    Thanked 3 Times in 3 Posts

    Default

    John actually posted about this on another thread. HIs post is a little easier to understand. I find this page to be very helpful. It is about the 4th or 5th post down.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •