- From: robglidden <notifications@github.com>
- Date: Thu, 14 Mar 2024 12:47:40 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 14 March 2024 19:47:45 UTC
@mirisuzanne: > 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. Separate from syntax, I am not sure I fully understand. To me, "access" couldn't happen at either the layers or scope proximity step in the cascade. It must happen before, I assume in the context step, and would pass first through the element-attached styles (style attribute in cascade 6) step. So [to me](https://github.com/WICG/webcomponents/issues/909#issuecomment-1971878378), between an attribute syntax and @layer syntax, an @layer syntax just seems more intuitive because it states access and priority in a single declarative syntax, though not a single operation, and other syntaxes could be fine too. But I assume a web browser implementor might look at this differently. -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/909#issuecomment-1998305361 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/909/1998305361@github.com>
Received on Thursday, 14 March 2024 19:47:45 UTC