[Bug 15447] support for document.write should not be required

https://www.w3.org/Bugs/Public/show_bug.cgi?id=15447

Henri Sivonen <hsivonen@iki.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #6 from Henri Sivonen <hsivonen@iki.fi> 2012-01-09 09:09:58 UTC ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, 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

Status: Rejected
Change Description: no spec change
Rationale: document.write support is needed for compatibility with Existing
Content (see
http://www.w3.org/TR/html-design-principles/#support-existing-content ) such as
this bug report itself. (View Source and you'll find a document.write call in a
script on this page!) Therefore, it would be bad to change the description of
document.write to be less reality-based.

The reporter says his/her planned to be planned user agent may ignore parts of
standards, so it doesn't matter what the standard requires. Thus,
document.write doesn't need to be made optional in the standard.

Note that the standard allows user agents to support the XML serialization
without supporting the HTML serialization, so if you wish to ignore inelegant
parts, you may ignore the entire HTML serialization and just implement the XML
serialization. However, note that when scripting is enabled, processing the XML
serialization involves blocking the parser, too, so you don't get rid of the
concept of parser-blocking scripts just by not implementing document.write.

Regarding point 5 in comment 3: It's possible to support document.write without
stalling parallel downloads. I've implemented it. And documented how to do it:
https://developer.mozilla.org/en/Gecko/HTML_parser_threading

-- 
Configure bugmail: https://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 Monday, 9 January 2012 09:12:15 UTC