25467 2014-04-25 22:30:58 +0000 [imports]: Dynanically added imports should block following imports. 2014-04-29 23:38:35 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC Linux RESOLVED WORKSFORME P2 normal --- 25470 1 morrita dglazkov mike public-webapps sorvell public-webapps-bugzilla oldest_to_newest 104472 0 morrita 2014-04-25 22:30:58 +0000 Currently dynamically added imports behaves as if it is @async applied. This should change. It should block following imports, in terms of script execution. For example: ---- <link rel=import href=a.html> <script> var currentDocument = document.currentScript.ownerDocument; var b = currentDocument.createElement("link"); b.rel = "import"; b.href = "b.html"; currentDocument.appendChild(b); var c = currentDocument.createElement("link"); c.rel = "import"; c.href = "c.html"; currentDocument.appendChild(c); </script> <link rel=import href=d.html> ---- In this case, scripts in imports should be executed in order of [a.html, b.html, c.html, d.html] instead of current [a.html, (probably)d.html, (b or c).html, (b or c).html]. What's the motivation? We need this because in some case we want to dynamically load a set of imports has dependency in it. For example we might want to lazily load plugin-base.html and plugin-hmm.html, where plugin-hmm.html depends on plugin-base.html. 104476 1 morrita 2014-04-25 23:00:11 +0000 Hmm. Actually, the spec doesn't say anything about dynamically-added node. This is probably what is already written. Will keep this open for a while so that people can share their opinions if there are, then close. 104477 2 morrita 2014-04-25 23:01:33 +0000 Note that this makes sense as we now have explicit @async and we can use it anytime we want. There is no need for this ugly workaround. 104761 3 morrita 2014-04-29 23:38:35 +0000 This is how spec is written. Blink implementation is just wrong and have to be fixed.