shouldn't chrome-extension: and file: pages be supported too?
on chrome-extension: pages, the module script is fetched (successfully? no errors in the console) but nothing happens
on file: pages, the module script only logs a CORS error in the console: "Invalid response. Origin 'null' is therefore not allowed access."
i attached a sample extension, you can install it and open the options page, or just open the page.html from a file: url
file: has always worked before for testing things locally, and i think chrome extension development would benefit greatly from being able to use modules
kouhei@, it looks like there is active development happening on this issue. Could you please update on the latest and what the plan is? As part of predictability program, we have an OKR to resolve or have a concrete plan for highest starred bugs, and this one is #10 on the list.
Thanks!
At high-level, we are close to shipping.
The remaining implementation work that we must fix before ship:
- P0: fixing stability issues
-- We have known memory leak and crash cases we would like to fix.
- P1: getting the security primitives right.
-- Known issue w/ CORS. Other primitives seems alright (CSP/SRI/...)
We want to land before ship if possible:
- P2: Optimizations to the tree fetching algorithm which will give us 4x-10x speed-up from local testing.
- P2: Dynamic imports
CL level / daily status are actively communicated through module-dev@chromium.org.
