- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Fri, 27 Sep 2024 01:30:35 +0000
- To: public-css-archive@w3.org
> * a shadow tree that wants to register a custom property _for the outer page to use on it_ is _required_ to do so via a global stylesheet, communicated in a side channel. (or leave the property unregistered) If they register it in the shadow, the outer page won't be allowed to set it.
Isn't this true for both variants of this proposal?
I wonder if we can solve it using the import/export mechanism we discussed on #10808 where we have an import/export semantic for those names to avoid the side-channel.
> no idea how we'd expose these distinctions via the OM. The methods only take a property name.
OK I understand what proposal means now. It's flexible which is good, but I think this will be extremely confusing. You can have the following be true:
```css
/* in outer scope */
my-element { background: var(--accent )}
/* in inner scope */
:host { color: var(--accent) }
```
In dev-tools or other reflection , it would look like:
```css
background: var(--accent);
color: var(--accent);
```
But the colors could be different based on where they're set.
--
GitHub Notification of comment by noamr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10541#issuecomment-2378230744 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 01:30:36 UTC