- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Fri, 12 Jul 2024 23:56:58 +0000
- To: public-css-archive@w3.org
I agree it would be useful (seemly in several situations). With @noamr's original proposal, there was a more clear distinction between the value we're grabbing (a selector syntax) and the place we're using it (in a declaration value). Once you put those both into selectors, using the same syntax, it's hard to know which is defining the parameter and which is accessing it. I think there's been progress on disentangling the `attr()` proposal - removing the problematic bits, so that it can move forward. This feature is a bit different, but they work in a similar space, so there may be some crossover. For this use-case specifically, the proposal only seems to address exact match. Is that good enough to solve most use-cases here? Those are my initial reactions. I'm not an editor on the selectors spec, so it would be good to get input from @tabatkins or @fantasai as well. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10567#issuecomment-2226545200 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 12 July 2024 23:56:59 UTC