- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Sep 2021 17:48:11 +0000
- To: public-css-archive@w3.org
Note that attribute selectors with `[tag]` wouldn't work, because then there is no way to target an actual `tag` attribute. I suspect the `:is()` idea wouldn't work, as we likely don't want to have special parsing rules for within `:is()` compared to outside `:is()`. Note that `x*` might work for element selectors but not attribute names, since `[a*=b]` already has a defined meaning. Unless we mandate a space after the wildcard? There is precedent for that sort of thing, with space around `-` and `+` in `calc()`. Both `a*` as well as `[a* =b]` are currently invalid. I think the wildcard approach would be my personal preference. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6571#issuecomment-911919635 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 2 September 2021 17:48:13 UTC