- From: Domenic Denicola via GitHub <sysbot+gh@w3.org>
- Date: Mon, 17 Oct 2016 19:17:46 +0000
- To: public-houdini-archive@w3.org
domenic has just created a new issue for https://github.com/w3c/css-houdini-drafts: == [worklets] could the module responses cache and custom fetch steps be simplified? == I just realized that instead of customizing the fetch step, you might be able to get away with something simpler. Namely, say: "Each `Worklet` has a **module map**, which is a [module map](https://html.spec.whatwg.org/multipage/webappapis.html#module-map), initially empty. Then, in the definition of [set up a worklet environment settings object], say that your module map algorithm returns the associated `Worklet`'s module map. And then, remove the "perform the request" customization entirely. Also, update to use [fetch a module worker script tree](https://html.spec.whatwg.org/multipage/webappapis.html#fetch-a-module-worker-script-tree) and check that the arguments match, as that changed a bit. I think this works!? The whole point of this customization was just to get a module map that's shared across all `WorkletGlobalScope`s associated with a given `Worklet`, right? But if that's the case, it's easy to accomplish just by customizing the `WorkletGlobalScope`'s environment settings object's module map algorithm. Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/324 using your GitHub account
Received on Monday, 17 October 2016 19:17:53 UTC