I have been working for months on refining an approach to tableless (or near tableless) skins that relies 100% on CSS for look and feel.  I couldn't make a pure CSS relient skin that I was happy with, and after considerable trial and error, ended up with skins that have a one-row table.   I thought that I was finally on the verge of having a package I could make available free to the DNN Community, but I have somehow created a set of skins with very strange behavior that I have been unable to resolve..

When the skin initially loads in "edit" mode (admin privileges) it looks good until I pass the mouse cursor over one of the container's dropdown menu links at which point all the containers disapear from the screen.  If I hold the cursor over one of the links ("settings" for example)  I can access and make changes to the module properties, but as soon as I finish, all containers disapear from the screen.  The code, however, does not disappear.   "View source" displays everything that should be there.

When the page is displayed in "public" mode, everything looks fine. I have previous iterations and other variations of this skin that work ok..  The most recent work involved trying to resolve display differences created by the way IE and Firefox handle the box model, especially in SOLPARTMENU.  .

If anyone is interested in taking a look at the package, (there are a few containers as well) with an eye toward helping me track the causes of this, I would be thrilled to send to a few people.

thanks for any potential help.

I just sent it - I'm not ready to post anything or public download just yet.

Any other takers?
thanks

The problem was occurring initially in both, then it suddenly started working ok in Firefox.  Still very strange in IE.  It appears to be related to mouseovers, as moving the cursor over the menu also causes the containers to disappear.  I have had some problems with priority of display (z-index)  with my previous attempts at CSS skins,  menus would sometimes appear behind the containers, so I assigned high values to menu items in the stylesheet which seemed to solve that issue. I suspect that that may be at the root of my current dilema.  I do not know how to determine what the computed z-index value of a block element when it is displayed.

As far as your post above, I do not think you can use absolute positioning for divs that occur after divs  that have been relatively positioned.- (well, you CAN, bur it really screws up your display be cause they use different points as a reference.)