This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Please enumerate the situations where as a side effect of a parse document.write() may be called and is not a no-op. (I.e. document.write() is a re-entrant call to the parser.) Please specify that in situations other than the enumerated ones, a re-entrant call to document.write() is a no-op. (This may end up being an empty set of situations.) The enumeration should include at least popping an HTML or SVG <script> off the stack. The enumeration might include popping an <svg> element off the stack (and firing a load event for it).
There's no way to list all the cases, since it depends on SVG and MathML, and those change regularly. When document.write() is called when the insertion point is undefined (which happens for all cases except the processing of HTML's own <script> element), document.write() calls document.open() which blows away the entire document. As currently specified, this happens for SVG's <script> too. I propose to leave it that way, thus sidestepping the entire issue and preventing SVG images from relying on document.write() as well. Reopen if you disagree.
This bug predates the HTML Working Group Decision Policy. If you are satisfied with the resolution of this bug, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.