- From: <bugzilla@jessica.w3.org>
- Date: Fri, 28 Feb 2014 19:14:23 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24848
Dave Herman <dherman@mozilla.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dherman@mozilla.com
--- Comment #3 from Dave Herman <dherman@mozilla.com> ---
Just to be clear:
- <module> is an HTML construct and out of scope for ES6.
- Instead, <module> (as well as the browser's default `System` loader) needs to
be spec'ed as a web spec.
- The touch points for ES6 modules and HTML imports include at least the
following requirements:
* HTML imports should be able to register ES modules in the system registry.
* While HTML imports want to be as concurrent as possible, the interaction with
modules should avoid unnecessary races between multiple imports or imports and
the main document deciding where to fetch modules' source from (since they can
appear in <module>).
Dave
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 28 February 2014 19:14:25 UTC