Re: [w3c/webcomponents] Rejecting CSS Modules in Workers (#854)

It's a good point that importing a CSS module in a Worker can be compared to trying to instantiate a constructable stylesheet, and I'm leaning towards the parse error approach based on this reasoning.

Although, this does seem subject to change depending on the outcome of #839 and I think any conclusion we might reach here would at least have to be revisited based on how that turns out.  For example say that we end up with a syntax that allows someone to write this sort of thing:
```import something from "./example" with type: typeThatDoesntExist```
Perhaps the mechanism that would fail the above should also be used to fail
```import sheet from "./example" with type: css``` when used in a Worker.

In any case I don't think it needs to block [this implementation](https://chromium-review.googlesource.com/c/chromium/src/+/1799923) as long as we're behind a flag and not really locked in to any decision.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/854#issuecomment-555263853