Re: order of AudioWorkletGlobalScope script application

Since this is already specced in the worklet spec, I don't think we need to
redefine our own storage for this purpose. We can simply use this notion
and add a link to the worklet spec.

Also it seems like this follows the order of 'fetching', not parsing. Is
this what we want? Can we import multiple files concurrently?

On Thu, Sep 29, 2016 at 7:32 AM Joe Berkovitz <joe@noteflight.com> wrote:

> Hi Ian,
>
> A question came up yesterday in conversation, about the order in which
> imported scripts are applied to a WorkletGlobalScope. I realized that we'd
> never discussed this in the WG, and that it would be desirable to apply
> scripts to every global scope in a consistent order. My guess was that this
> order should be the order in which Promises returned from various
> importScript() calls are resolved, and that a given Worklet would need to
> maintain some kind of internal list that captured the scripts' parse
> results this order.
>
> On perusing the Worklet spec more carefully, I found this:
>
>     https://drafts.css-houdini.org/worklets/#module-responses-map
>
> Is the "module responses map" the very thing I was thinking about?
>
> Thanks for your help!
>
> Best,
>
> .            .       .    .  . ...Joe
>
>