I don't have the proper screen to read the code at the moment, but what if build script is powerful enough to inject specified files? Would that replace the runtime feature request, at least for now?
(That however does imply Gaia app will not work w/o a build step) On Friday, March 6, 2015, Julien Wajsberg <[email protected]> wrote: > Hey, > > here is a little piece of feedback. > > I tried using HTML imports for Web Components recently [1], and it > actually worked well and was quite nice to use without any framework. I > can understand why React and such don't care about this, but if we want > to stay closer to the metal it's a useful piece of spec. > > However there is a real performance impact when loading it: first we > need to load the imported HTML file, then the JS and CSS files inside > the import, then use registerElement on the main document, and only then > the component is usable. > > Clearly the performance issue would need to be fixed for HTML Imports + > Web Components to be adopted. > > > [1] > > https://github.com/mozilla-b2g/gaia/compare/master...julienw:simple-header#diff-56289627d91906a9c3b0f834ef19f514 > > Le 05/03/2015 12:28, Anne van Kesteren a écrit : > > I thought it might be good to give a quick update. As announced > > https://hacks.mozilla.org/2014/12/mozilla-and-web-components/ we're > > not doing HTML imports. We have not found an internal need and > > feedback from Ember, React, and peers in the standards community > > suggest that iterating on JavaScript modules and new fetching > > primitives is sufficient for now. > > > > For custom elements and shadow DOM there's documents where we keep > > track of outstanding issues: > > > > * https://wiki.whatwg.org/wiki/Custom_Elements > > * https://github.com/w3c/webcomponents/wiki/Shadow-DOM:-Contentious-Bits > > > > Unfortunately it does not look like agreement will be found soon. The > > high-level bit of feedback that keeps coming back is that we need to > > find a way to get layout fast and code more manageable. How exactly we > > should get there is still unclear. > > > > There will be a meeting > > https://lists.w3.org/Archives/Public/public-webapps/2015JanMar/0661.html > > (April 24, Mountain View) to discuss shadow DOM in particular and > > perhaps http://lanyrd.com/2015/extwebsummit/ (April 19, San Francisco) > > can also be used as a discussion venue. > > > > We have had some discussions around within Mozilla in Portland. > > Perhaps we should have another one over Vidyo? Hearing from Gaia again > > now v3 is underway would be useful. (Tentative suggestion: Thursday > > March 12, 9AM PST.) > > > > > > >
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
