Re: [css-houdini-drafts] [worklets] dynamic import()

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?

The main reason to block dynamic `import()` is the same reason we block `fetch()`; to make it clear worklets are not supposed to have that kind of code.

-- 
GitHub Notification of comment by annevk
Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/506#issuecomment-342738954 using your GitHub account

Received on Wednesday, 8 November 2017 07:57:48 UTC