Re: Script Pre-Loading Proposal on WhatWG

This is a pretty loaded area and it overlaps with work TC39 is doing in
Modules.

My view is that both "async" and "defer" should be supported as well as a
flag that marks a script as "disabled" (downloaded but not even compiled).
I've floated the idea before of allowing <script> elements to have groups
which are otherwise async but which are internally apparently ordered (via
document order) and I'm glad to see Ian taking it up here. I don' think his
particular syntax is workable, but otherwise it's a good start. Instead of
using depencies="...", i'd prefer they all just have a group="...." which
uses a common value for elements.

In terms of explaining how that would work, there's some mechanism in ES6
script loaders that can make sense of it, but not with shared global scope.


On Wed, Jul 10, 2013 at 12:05 PM, Appelquist Daniel (UK) <
Daniel.Appelquist@telefonica.com> wrote:

> FYI:
> http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2013-July/039960.html
>
> Thoughts? Opinions? This would seem to be an issue we might take a view
> on, considering the TAG's new focus.
>
> Dan
>