- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Fri, 27 Sep 2024 00:35:44 +0000
- To: public-css-archive@w3.org
> > What made sense to me (as mentioned in the minutes), is that `@property` in shadow-scoped styles makes the property "private" (not inherited from the outer scope), which fixes the type mismatch issue. So internal uses of the property would fall back to the `@property`'s `initial` value rather than to what's inherited from the outer scope. > > This can also be useful as a way to "undo" the `@property` definitions inherited from the outer scope. > > I think this doesn't provide a clear answer for what to do about elements that can be styled from both inside and outside - e.g. `:host` or `::part()` or also the property value observed inside slots. Those have to be defined in the outer scope. `::part()` (and `::slotted`) are an API surface, so the outer scope needs to know about it. They'll be naturally inherited like today. > > My thinking was that with the tuple we could track both property values on these elements and inherit the outer value of the property inside of slotted elements. Can you give an example of what this would look like? -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10541#issuecomment-2378182675 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 27 September 2024 00:35:45 UTC