W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2014

Re: HTML imports in Firefox

From: Boris Zbarsky <bzbarsky@mit.edu>
Date: Mon, 15 Dec 2014 14:09:07 -0500
Message-ID: <548F31D3.1080709@mit.edu>
To: public-webapps@w3.org
On 12/15/14, 1:10 PM, Ashley Gullen wrote:
> Why would modules affect the decision to ship HTML imports?

Because the interaction of the various import systems with each other 
needs to be specified, for one thing.

But more to the point, we're not shipping imports because we've gotten 
feedback from a number of people that imports are not solving the 
problems they actually need solved.  We'd prefer to not ship imports and 
then need to ship yet another HTML import system that solves those problems.

> The webcomponents.org <http://webcomponents.org> polyfill for imports
> has a couple of caveats, so it doesn't look like it's totally equivalent
> and portable with browsers with native support, like Chrome which has
> shipped it already.

Chrome has shipped a lot of things in this space already.  Feel free to 
mail me privately for my feelings on the matter.  chrome shipping 
something is not sufficient reason to ship something we're pretty sure 
is deficient, I'm afraid.

Received on Monday, 15 December 2014 19:09:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:32 UTC