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

HTML imports in Firefox

From: Ashley Gullen <ashley@scirra.com>
Date: Mon, 15 Dec 2014 18:10:00 +0000
Message-ID: <CAABs73hiYOWXPrR4KR_OzJw+pdqDQZD_d4nfLQGs=LSYj4S8Xg@mail.gmail.com>
To: public-webapps@w3.org
I was a little surprised to read Mozilla don't plan on shipping HTML
imports and will re-evaluate after modules are supported:

Why would modules affect the decision to ship HTML imports? Imports get you:

- the ability to import style and markup, not just script
- a tree-like dependency structure with automatic deduplication
- parallel loading/parsing
- ability to start fetching sub-resources before script has parsed and run
- tidy markup (sub-resources go in their import documents, not all dumped
in to <head>)

I don't see how modules has any impact on this. In a web environment where
components will commonly use style, templates and the like, imports seem
like the obvious choice over modules.

The 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. I'm keen to see
Mozilla ship this feature too.

Received on Monday, 15 December 2014 18:10:32 UTC

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