- From: Miriam Suzanne <notifications@github.com>
- Date: Wed, 13 Mar 2024 10:16:18 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 13 March 2024 17:16:22 UTC
I would still be concerned that this confuses the concept of layering with the concept of scope. I don't believe it's a good idea to encourage a layer-per-component approach (e.g. a 'buttons' layer). While this sort of layering-as-access mechanism doesn't require you to do that, it very clearly encourages it. Now as an author I will want to create individual layers for each custom element, so that element can reference the layer. I think it's a good idea to allow layering of external styles, but dangerous to use layers as _the way we define access to those styles_. I think `@scope` would be a much better control for defining what styles are pulled in - and then layers could be used on both ends to help define the cascade of those styles when applied. -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/909#issuecomment-1995046971 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/909/1995046971@github.com>
Received on Wednesday, 13 March 2024 17:16:22 UTC