W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2010

[Bug 9767] Consider ignoring document.write() when IE ignores it if comes from the network task source

From: <bugzilla@jessica.w3.org>
Date: Wed, 14 Jul 2010 02:02:34 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1OYrIw-0008CV-2V@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9767


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

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




--- Comment #17 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-07-14 02:02:32 ---
The solution in comment 8 seems to make document.write()s in timeouts act
differently based on whether the parser has finished or not, which seems bad.

The solution in comment 16 makes the resulting document depend on the network.
It's bad enough that we let script load order depend on the network, but having
it change the resulting source document seems excessively bad. It also seems
like this would still cause the page to go blank in the case of the scripts
taking longer to load than the page (i.e. nothing seems to prevent the scripts
from being read after the EOF is consumed). In fact I don't really follow how
you're preventing the EOF from being consumed at all... surely as soon as you
know there's an EOF, it's consumed? Are you just appending it at random points
in the stream (i.e. after whatever you happen to have received from the network
so far)?

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: Accepted
Change Description: see diff given below
Rationale: The problem is real; I've gone with the solution in comment 10 for
now.

-- 
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 Wednesday, 14 July 2010 02:02:36 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:30:52 UTC