- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 27 Sep 2024 01:00:49 +0000
- To: public-css-archive@w3.org
Enhancing custom property names to a (tree scope, property name) tuple does solve some of the issues: * host element can be styled with *both* versions of the property * so can ::part() It has some issues too: * 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. * no idea how we'd expose these distinctions via the OM. The methods only take a property name. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10541#issuecomment-2378204738 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:00:50 UTC