24808 2014-02-25 18:47:13 +0000 [imports]: document.write() in imports should do nothing. 2014-05-14 00:17:23 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC Linux RESOLVED FIXED P2 normal --- 24623 20683 24042 1 morrita dglazkov annevk bruno bugs bzbarsky ian mike public-webapps public-webapps-bugzilla oldest_to_newest 101362 0 morrita 2014-02-25 18:47:13 +0000 Spinned out from Bug 24042. 101365 1 ian 2014-02-25 18:50:34 +0000 Per the discussion in bug 24623, I think this is unnecessary, unless we're trying to explicitly kill document.write() for purity reasons (in which case I'm happy to get behind this, if we're clear that we're not doing this for technical reasons). 101377 2 bugs 2014-02-25 19:23:44 +0000 FYI, I'd be happy to start killing document.write (well, document.open) And one way to do it is to not expose new features to it. 101379 3 dglazkov 2014-02-25 19:26:10 +0000 (In reply to Olli Pettay from comment #2) > FYI, I'd be happy to start killing document.write (well, document.open) > And one way to do it is to not expose new features to it. Sounds good to me. 101382 4 morrita 2014-02-25 19:30:35 +0000 Basically this change makes imports more like external scripts where document.write() is voided. So it aligns the kill-document-write path. 103889 5 morrita 2014-04-15 18:14:08 +0000 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. 103893 6 bzbarsky 2014-04-15 18:20:03 +0000 Please do not monkeypatch other specs. Talk to the html spec editor about getting this case handled. 103897 7 morrita 2014-04-15 19:52:25 +0000 (In reply to Boris Zbarsky from comment #6) > Please do not monkeypatch other specs. Talk to the html spec editor about > getting this case handled. We're thinking about making HTML Imports part of WHATWG HTML once the churn is settled. We want to do that exactly because the large part of the spec is a set of monkey patches. 105925 8 ian 2014-05-13 21:59:24 +0000 This is resolved now, no? Calling document.write() on an import doc throws, and calling it on a master document just works as already specified, nothing new. 105935 9 morrita 2014-05-14 00:17:23 +0000 (In reply to Ian 'Hixie' Hickson from comment #8) > This is resolved now, no? Calling document.write() on an import doc throws, > and calling it on a master document just works as already specified, nothing > new. You're right. This was reopened to request removing monkey-patching. As it is merged to HTML, this will no longer an issue. closing.