Re: [css-houdini-drafts] import() setup is inefficient

I think I set it up this way to make sure that "fetch a module script 
tree" had an appropriate settings object. But yeah didn't consider the
 service worker leaking of information.

We'll want to probably specify that all of the fetching (and import 
pre-processing, etc) occurs separately from the actual script creation
 (with the actual execution context).

@domenic does splitting up "fetch a module script tree" into; "fetch a
 module script tree resources" and "create a module script tree" or 
similar, make sense? If so I can start working on a PR for whatwg/html

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

Received on Friday, 24 June 2016 18:32:41 UTC