The most important problem to iron out with HTML Import + ES6 Loader is the timing confusion. Both systems use a combination of asynchronous and blocking-for-dependents loading. The issues could be explored with any of the existing ES6 pre-standard Loader implementations. (If the developer uses an ES6 Loader in an HTML Import, the registry will be automatically shared).
On Tue, May 27, 2014 at 8:28 AM, Matthew Robb <[email protected]>wrote: > On Tue, May 27, 2014 at 8:09 AM, John Barton <[email protected]>wrote: > >> >> >> >> On Fri, May 23, 2014 at 5:04 PM, Ian Hickson <[email protected]> wrote >> >>> >>> What/where would be the best place to define such a system, >>> >> >> Github. >> >> >>> and how would >>> we hook all the specs together to use it? >> >> >> Define a "System" object for ES6 that implements the ES6 Loader API and >> extends it to dynamically load CSS and HTML. >> >> jjb >> >> > This is basically what I was trying to say. Additionally I was suggesting > that you also specify HTML Imports as using the System loader and thus the > shared registry and dependency tree. > >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
