W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2011

[Bug 14275] This non-normative box is not very clean. After all, using DOM methods or innerHTML also could make DOM not correspond source code of document (heck, older versions of IE did some transformations). Also, as long you won't use async or defer I cannot think

From: <bugzilla@jessica.w3.org>
Date: Sun, 02 Oct 2011 18:06:27 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RAQQl-00035E-Iq@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14275

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ian@hixie.ch
         AssignedTo|ian@hixie.ch                |contributor@whatwg.org

--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-10-02 18:06:27 UTC ---
> After all, using DOM methods or
> innerHTML also could make DOM not correspond source code of document

This warning is talking about much more serious cases than that. For example,
if you document.write() the string "<plaintext>", the rest of the document is
turned to text, regardless. With innerHTML and DOM manipulation, you can't
cause the parser to parse parts of the document differently than it otherwise
would have.


> Also, as long you won't use
> async or defer I cannot think of case where document.write() would depend on
> network latency...

The case in which it does depend on latency escapes me right now, but I'm
pretty sure there is one...

Anyone remember what it is?

-- 
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 Sunday, 2 October 2011 18:06:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:05 UTC