[Bug 25715] [imports]: Unify loading and dependency resolution model with ES6 modules

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25715

--- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch> ---
I think what might make the most sense is for HTML to define the dependency
fetching system, including things like delaying loads until something needs the
dependency, precaching, deferring, etc, whether loads should block other
scripts from executing, whether to early-execute or late-execute when there's a
dependency chain, etc, and for the JS module system to just have hooks that
HTML bootstraps into this system. (We're going to need to have hooks anyway for
actually fetching things over HTTP.)

In the case of modules in particular, having all this would allow us to hook
modules into the dependency tree before actually fetching any files, so that
they could be lazily loaded without requiring multiple round-trips to fetch all
the dependencies once they _are_ needed.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 22 May 2014 22:57:40 UTC