On 11/11/05, Christian Heilmann <[EMAIL PROTECTED]> wrote: > The easier option is to hide the elements when you open your popout, > that way you keep the fix at least in the JavaScript and not in CSS, > HTML and JavaScript.
That solution hadn't occurred to me before, its rather elegant solution I must say. But its not necessarily the magic bullet for all situations. Take my application for example : I have quite a complex web application/database. Every page has a Help button that when clicked displays a popup div with context sensitive help for that page. There is no knowing which elements might be obscured by the help because the help is dynamic and I encourage users to help write the help (its actually stored in a wiki), Also the user can move the help popup around using the titlebar, so at times only parts of elements might be obscured, you can't visible: hidden part of an element. If on clicking help, all <select> elements were to disappear then the help would be confusing because it would reference elements that have disappeared. I can't move the elements around so they don't obscure each other for exactly the same reason, so the only solution left to me that I know of is the iframe shim fix. I suppose I could interrogate the position of all elements and set visibility: hidden if they overlap. Or I could mess around with the clip element for a while, but the requirement that the element is absolutely positioned is too high a price to pay, Anyway that solution is more complex than the iframe fix. Yes its a pain but it is a practical solution to a real world CSS problem, which is exactly what css-discuss is supposed to be about. And this question does crop up a least once a month on this list. > I avoided giving that solution as we really should not add extra > markup that even shows up in assistive technology as another document > just to fix a browser bug. Forms are hard to use as they are, no need > to confuse matters even further. The solution can go purely in the Javascript where it belongs, without affecting the markup or CSS at all. The JS can then be served up to IE only, so its not semantic. But even though its all in JS, it is a fix to a real world common CSS problem. Sam ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
