The Nightmare of IE6 SELECT tags
| IE treats all SELECT tags as having infinite Z-Index
(because Microsoft bizarrely chose to generate SELECT
tags through the operating system) so they show through
almost anything that is intended to float over them.
However, an IFRAME tag creates another document so
SELECT tags don't show through them. This allows for the widely used technique of backing a floated element with an IFRAME to protect it from any underlying SELECTs. If using SSL (https), IE treats IFRAME tags as insecure unless they have a safe SRC attribute value so one is needed to avoid the pop-up "mixed content" warning. The most consistent solution is to give a simple file name e.g blank.html (the calendar uses scwBlank.html). It would be preferable not to have a physical file in order to minimize clutter. However, if the file doesn't exist then Internet Explorer 6 browser settings can disrupt the page history. NOTE: It is quite possible for you to develop a page without encountering the problem yet users of the page may still get it. Consequently, the only complete solution I have found is to create an empty physical file. The best description I have found of problems with IFRAMEs in IE comes from Eric Costello in his article called Remote scripting with IFRAME . Of course he doesn't describe exactly the situation above but the similarity strongly indicates a common underlying bug in IE6. |