W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2013

[Bug 24042] New: [imports]: Parser should not wait on external resources inside imports

From: <bugzilla@jessica.w3.org>
Date: Mon, 09 Dec 2013 22:49:17 +0000
To: public-webapps@w3.org
Message-ID: <bug-24042-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24042

            Bug ID: 24042
           Summary: [imports]: Parser should not wait on external
                    resources inside imports
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: esprehn@gmail.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org
            Blocks: 20683

The HTML parser should continue tree building inside an import even if blocked
on an external resource.

As a result document.write() should also throw when the currentScript is inside
an import since the location of the write is arbitrary.

The result of this is that given:

<link rel="import" href="1.html">
<script src="slow.js"></script>
<link rel="import" href="2.html">
<link rel="import" href="3.html">
<x-foo></x-foo>
<script>
  console.log(1);
</script>

While slow.js is being downloaded the entire import tree (1.html, 2.html and
3.html) can be processed and constructed into DOM trees. When it finishes
loading the scripts that were queued while tree building these nested imports
and the top level import with the console.log should be executed in order. This
is conceptually similar to defer@ or async@ on <script>.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 9 December 2013 22:49:18 UTC

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