W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2014

[Bug 24808] [imports]: document.write() in imports should do nothing.

From: <bugzilla@jessica.w3.org>
Date: Tue, 15 Apr 2014 18:14:08 +0000
To: public-webapps@w3.org
Message-ID: <bug-24808-2927-3wJkthbu49@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24808

Morrita Hajime <morrita@google.com> changed:

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

--- Comment #5 from Morrita Hajime <morrita@google.com> ---
https://github.com/w3c/webcomponents/commit/6786e3c576334bbdd0254c4258c43e5199d9b6f2

I was confused but there are two cases to consider.

One is document.write() against the master document. As Hixie mentioned, it
just blows the document away. So we don't have do anything.

Another is document.write() for imports themselves. IIRC, it works for now. But
once we address Bug 24042 and UA delays script execution timing more
aggressively, the situation will change and document.write() won't work
anymore.

I don't have any immediate plan to address Bug 24042 as it needs more
consideration and ES6 <module> or <script defer> might resolve the underlying
problem for free. I however want to remove obstacles to attack it in the first
place.

So I disabled these document APIs for imports. It's a safety net, and I think
this is what Olli suggests.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 15 April 2014 18:14:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:24 UTC