- From: <bugzilla@jessica.w3.org>
- Date: Fri, 09 Jul 2010 18:49:48 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9767
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ian@hixie.ch
--- Comment #10 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-07-09 18:49:46 ---
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.
--
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 Friday, 9 July 2010 18:49:49 UTC