- From: <bugzilla@jessica.w3.org>
- Date: Sat, 10 Jul 2010 06:50:27 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9767 --- Comment #13 from Henri Sivonen <hsivonen@iki.fi> 2010-07-10 06:50:27 --- (In reply to comment #10) > That's a tough one. I think ignoring document.write() in scripts that are > asynchronously fetched for <script> elements inserted while the parser is > running, rather than them blowing the document away is reasonable. I'm not sure > that exactly maps to the explanation above, though. It would need a flag on the > <script> element set when the element is added to the document, based on > whether the parser is on the stack, and then for the script execution to set a > similar flag (using a counter as described above to be reentrancy-proof) that > causes document.write() to bail. That seems overly complex to the solution in comment 8. Is there a reason why ignoring document.write()s from scripts inserted after the end of parse is unreasonable (when the owner doc of the script is the document write() is called on)? -- 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, 10 July 2010 06:50:29 UTC