Re: System.import()?

and this is why XHTML... On Friday, August 21, 2015, Domenic Denicola wrote: > From: es-discuss [mailto:es-discuss-boun...@mozilla.org ] > On Behalf Of James Burke > > > > In the spirit of the extensible web, defining these lower level APIs and > more > > of the loader would make it possible to

Re: System.import()?

On Fri, Aug 21, 2015 at 8:12 AM, Domenic Denicola wrote: > No, custom elements cannot prototype the module tag, because custom elements > will always be parsed as unknown elements. So e.g. Ah, thanks for pointing that out. I was thinking more of the script src style of tag. The need for module b

RE: System.import()?

From: es-discuss [mailto:es-discuss-boun...@mozilla.org] On Behalf Of James Burke > In the spirit of the extensible web, defining these lower level APIs and more > of the loader would make it possible to use custom elements to help > prototype a tag. The custom element mechanism can be used in

Re: System.import()?

On Tue, Aug 18, 2015 at 11:36 AM, Dave Herman wrote: > https://github.com/whatwg/loader/blob/master/roadmap.md >From a loader/tool perspective, it seems like working out more of the Stage 1 items before many of the Stage 0 items will lead to higher leverage payoffs: the dynamic loading and module