Re: [w3c/webcomponents] CSS Modules (#759)

I agree that this part should have some deliberate design, even if it's disappointing to see a delay in what I think is a very critical feature for modernizing web development.

There is a path that's forward-compatible with either outcome of the `@import` discussion, which is to disallow `@import` for now, much like `CSSStyleSheet#replaceSync` does. At worst, this pushes dependencies between CSS modules into JS module wrappers, which is what would happen if `@import` in CSS modules retained non-module CSS `@import` semantics. That could be undone if/when `@import` is supported in the future.

Not that delaying CSS modules would likely delay HTML modules too, given the current HTML modules proposal's dependency on them.

But given the need to design `@import` carefully, how can we move that discussion forward? Is this issue/repo even the right place? Should it be in the CSSWG? Who needs to be involved? cc @tabatkins.

-- 
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/759#issuecomment-495709197