This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6257 - Please specify document.write()-safe points in the parse
Summary: Please specify document.write()-safe points in the parse
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NoReply
Depends on:
Reported: 2008-11-29 12:50 UTC by Henri Sivonen
Modified: 2010-10-04 14:32 UTC (History)
3 users (show)

See Also:


Description Henri Sivonen 2008-11-29 12:50:33 UTC
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).
Comment 1 Ian 'Hixie' Hickson 2008-12-29 23:50:37 UTC
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 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.
Comment 2 Maciej Stachowiak 2010-03-14 13:15:56 UTC
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:

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.