Re: [w3ctag/design-reviews] CSS Modules (#405)

@plinss and I are discussing this again in a breakout in [Cupertino](https://w3ctag.github.io/meetings/2019/12-cupertino/).

We'd note that there are additional variants of options 2 and 3 that could be considered, in particular:
* an option 2a that treats a failed `@import` as just something that gets dropped like in the rest of CSS, rather than causing the module to fail
* an option 3a that makes the CSSOM for such stylesheets readonly (although neither of us really like that)

Along those lines, it might be useful if the explainer says what happens when an `import` fails, for readers who aren't familiar enough with ES modules.  (I'm not!)

We're also concerned about relying on either the file extension (given that web behavior shouldn't depend on them) or the mime type (given the security issue mentioned above) to determine that it should be CSS, so it seems like there should be some syntax differentiation for stylesheet imports.

We're curious what the status of this is, and whether you have any thoughts on this or the previous comments?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/405#issuecomment-561304217