Re: [w3ctag/design-reviews] Declarative CSS Modules and Declarative Shadow DOM `adoptedstylesheets` attribute (Issue #1000)

sorvell left a comment (w3ctag/design-reviews#1000)

> We definitely don't want to back ourselves into a corner with shadowrootadoptedstylesheets 

That's very reasonable. I think it would be valuable to add a small section to the explainer about this.

> I can think of several ways this could be handled, the most natural being a fragment identifier

It seems like this would have a shadowroot visibility issue.

> shadowrootadoptedstylesheets is built on module script importing

Not sure what you mean here. It's just (currently) limited to CSSStyleSheet. While css modules produce these, you can also just construct one in JS.

> This can be addressed separately with a generic way to add element references to the module ma

Though not directly relevant to elements and modules, this issue does suggest the ability to tie specifiers to urls, which might be worth some thought and/or an explainer mention: https://github.com/whatwg/html/issues/12163

> Have you tested it in Firefox with lift-adoptedstylesheets-restriction enabled?

Yeah, `@import` rules work in Firefox with the setting. This makes sense since the sheet isn't constructed.  If @import were added to constructed sheets/modules as I hope it can be, this would no longer be a reason to prefer using non-constructed sheets, but I do think there are still other reasons to support non-constructed sheets.

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

Message ID: <w3ctag/design-reviews/issues/1000/3948405590@github.com>