Adding out-of-band dependencies for a module

David Herman dherman at
Tue Aug 12 10:53:20 PDT 2014

On Aug 11, 2014, at 5:06 PM, Ian Hickson <ian at> wrote:

> So I'm trying to figure out how to spec the HTML spec's Loader.

We should coordinate -- I've been actively working on this (not the spec per se, but the design) with people engaged in the JS modules work. The HTML default loader design has some requirements that touch on existing JS ecosystems and practices, so we need to be sure we don't spec it in isolation.

> One of the things that we're likely to add as part of this is a generic 
> dependency system.

You've mentioned this to me before, but I'm afraid I haven't seen any clear rationale written up anywhere, nor a good description of what this means. One thing it might mean is a resource-fetching dependency system, meaning that for any two elements A and B that require fetching a network resource, you can state that A depends on B, meaning that whenever A's resource is fetched, B's resource should be fetched too and the system should not consider A's fetch complete until B's fetch is complete. If that's what you mean, I'm skeptical that an attribute is the right level for programmers to express this kind of resource grouping. In particular, HTTP2 and the TAG's work on package management are better approaches to grouping network resources than scattering dependency attributes across a DOM tree.


More information about the es-discuss mailing list