- From: Hiroki Nakagawa via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Nov 2017 09:32:31 +0000
- To: public-houdini-archive@w3.org
> I wonder how worklets work with the opaque origin setup if their modules can have non-dynamic imports. Did you review that @domenic? Or maybe the opaque origin is assigned after all dependencies are fetched? IIUC, non-dynamic imports are handled as sub-resources of the owner document like ```addModule()```, so the opaque origin is not a problem. Chromium implemented this behavior and there are [WPT tests](https://github.com/w3c/web-platform-tests/blob/master/worklets/resources/import-tests.js#L29) for the case. -- GitHub Notification of comment by nhiroki Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/506#issuecomment-342761129 using your GitHub account
Received on Wednesday, 8 November 2017 09:32:34 UTC