- From: Ian Kilpatrick via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 Jun 2016 18:40:41 +0000
- To: public-houdini-archive@w3.org
Yeah that's right; as a `WorkletGlobalScope` can effectively be "cloned", i.e. the engine can create a new `WorkletGlobalScope` on demand, e.g. when spinning up a new paint thread for example. So in the ideal world, we'd have a module-map* associated with the main `Worklet` object, which contains the url->source-mapping, and when we need to create a new `WorkletGlobalScope` post-task all of the required url->source-mapping over to a new thread to be created into actual scripts. The bug is basically about establishing the invariant "within a single worklet object, modules are never fetched more than once" instead of "global scope object". -- GitHub Notification of comment by bfgeek Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/229#issuecomment-228426987 using your GitHub account
Received on Friday, 24 June 2016 18:40:46 UTC