- From: <bugzilla@jessica.w3.org>
- Date: Sat, 11 Sep 2010 18:10:51 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10340 --- Comment #2 from Adrian Bateman [MSFT] <adrianba@microsoft.com> 2010-09-11 18:10:50 --- In our testing, even Chrome6 does not [OverrideBuiltins] in the iframe case. They appear to first lookup the real "document" before getting the window from the iframe. If Chrome supported [OverrideBuiltins] for iframes, then we would expect both "doc" and "win" below to alert the Window--but that is not the case. To answer your question, both IE8 and IE9 do not OverrideBuiltins for <iframe name="document">. Here's our interop report and test case for your verification: <!DOCTYPE html> <html><head><title>window [OverrideBuiltins] and iframes</title></head> <body> <iframe name="document2" src="http://www.bing.com/"></iframe> <iframe name="document" src="http://www.google.com/"></iframe> <div id="toString"></div> <span id="testing"></span> <script> onload = function () { try { var spn = testing; // Confirm this functionality is supported } catch (ex) { } try { var doc = document; } catch (ex) { } try { var win = document2; } catch (ex) { } try { var func = toString; } catch (ex) { } // Results: Chrome6 Firefox3.6 IE8 IE9 alert(spn); // HTMLElement undefined HTMLSpanElement HTMLSpanElement alert(doc); // HTMLDocument HTMLDocument HTMLDocument Document alert(win); // DOMWindow Window Window Window alert(func); // [native code] [native code] [native code] [native code] } </script> </body> </html> -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Saturday, 11 September 2010 18:10:53 UTC