24643 2014-02-13 01:27:55 +0000 Want a extension point to extend criteria to fire DOMContentLoaded 2014-04-07 21:46:44 +0000 1 1 1 Unclassified WHATWG HTML unspecified PC Linux RESOLVED INVALID blocked awaiting response to comment 6 (please remove this when replying) P2 normal Unsorted 23526 24632 1 morrita ian annevk dglazkov ian mike contributor oldest_to_newest 100463 0 morrita 2014-02-13 01:27:55 +0000 HTML Imports patches "the end" [1] section of the parser algorithm so that the parser waits until all script-blocking imports are loaded[2] It would be great if HTML exposes some extension point to add another criteria for DOMContentLoaded event emission without monkey patches. [1] http://www.whatwg.org/specs/web-apps/current-work/multipage/the-end.html#the-end [2] http://localhost:8000/spec/imports/#additions-to-tree-construction-algorithm 100486 1 annevk 2014-02-13 10:17:07 +0000 [2] is http://w3c.github.io/webcomponents/spec/imports/#additions-to-tree-construction-algorithm 100553 2 morrita 2014-02-13 18:40:16 +0000 (In reply to Anne from comment #1) > [2] is > http://w3c.github.io/webcomponents/spec/imports/#additions-to-tree- > construction-algorithm *facepalm* Thanks for the catch. 100630 3 ian 2014-02-14 21:47:23 +0000 Isn't import something we just want to merge into HTML in due course, like we did for <template>? 100808 4 morrita 2014-02-18 18:04:05 +0000 (In reply to Ian 'Hixie' Hickson from comment #3) > Isn't import something we just want to merge into HTML in due course, like > we did for <template>? We're thinking about this but not decided yet. If the Imports spec stays small in coming iterations, it'd be better to merge it into HTML. We need a bit more polish before that point though. @dglazkov might have better idea. 100809 5 dglazkov 2014-02-18 18:08:34 +0000 (In reply to Morrita Hajime from comment #4) > (In reply to Ian 'Hixie' Hickson from comment #3) > > Isn't import something we just want to merge into HTML in due course, like > > we did for <template>? > > We're thinking about this but not decided yet. If the Imports spec stays > small in coming iterations, it'd be better to merge it into HTML. We need a > bit more polish before that point though. > > @dglazkov might have better idea. Yes. We should totally merge it into HTML spec in due course. Imports are designed at HTML layer. 100999 6 ian 2014-02-20 20:26:23 +0000 If we're going to merge anyway, let's not worry about hooks (just patch it for now). Do we have an ETA for when this should get merged? (Do we have multiple vendors on board?)