- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 Apr 2022 22:30:40 +0000
- To: public-houdini-archive@w3.org
Further musing: the host element problem isn't unique to the host element. ::part() pseudos also mean both the outer and inner trees have direct styling access to an element, with the styles from both scopes intermixing, and thus both have claims to the registration of a particular property on the element. So yeah, as far as I can tell this is just an unsolveable problem with the primitives we have available to us. Even if we track the tree scope that the rule came from (so we can parse it with the corresponding registration), that doesn't stop the confusion that would come from two different "meanings" of the same property name being used on a single element at the same time, and one winning while code expects the other to win. Uniquifying names continues to be the only reasonable solution to this, and nothing we can do to help with uniquification seems like it would be significantly better than just hand-uniquifying, so we can't justify the added complexity. I'm gonna just add some text to the spec talking about this issue and suggesting uniquification. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/939#issuecomment-1100446439 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 15 April 2022 22:30:42 UTC