Problem: IE gives a mixed content security warning when using an IFRAME.
Cause: IFRAME without a "SRC" attribute is used inside of a page loaded using HTTPS
Fix: use the following:
<iframe src="">Fix description:
IE requires a source attribute on IFRAMEs to be considered secure. If the code of the page is planning on using an IFRAME to do something else besides load an external page, it still needs this SRC attribute to get around this "bug" in IE.
Applies to: Tomahawk popup and HTML editor
Problem: IE puts all SELECT items at maximum z-index
Cause: IE uses a windows control (MFC?) for SELECT controls. These windowed elements don't behave correctly - they ignore many CSS styles and do not render correctly in a browser.
Fix: as many know, there is a "hack" in IE that an IFRAME can go over a SELECT, but it doesn't not ignore z-index. So putting an IFRAME below a control makes sure that that control appears over SELECT boxes. I have some more input on this
Extra information: To put an IFRAME below an control is a JS pain, as can be seen with the Tomahawk popup and it not always appearing in the right location. I have found that an IFRAME inside of a DIV, still works. See below:
<div style="z-index: 5; position: absolute; top: 25px; left: 25px;">
<iframe src=""> style="position: absolute;
height:_expression_( parentNode.scrollHeight);
width: _expression_(parentNode.scrollWidth);
z-index: 1;"></iframe>
<div style="position: relative; z-index: 2;">The popup contents would go here</div>
</div>
Fix description:
If this two-layered DIV approach is used, the IFRAME is always the same size as the parent. There is no _javascript_ needed. The only bad side affect is that positioning CSS styles should be given to the parent DIV and all other styles (fonts, colors, etc) should be given to the inner DIV.
<iframe src=""> style="position: absolute;
height:_expression_( parentNode.scrollHeight);
width: _expression_(parentNode.scrollWidth);
z-index: 1;"></iframe>
<div style="position: relative; z-index: 2;">The popup contents would go here</div>
</div>
Applies to: Tomahawk popup
The popup authors may choose to use my 2nd fix if they want, but the first fix really needs to be put into the code to stop the IE warning under HTTPS
Hope that helps,
Andrew

