- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 Sep 2021 00:01:56 +0000
- To: public-css-archive@w3.org
Hm, not sure why I thought `__bar` was a valid element name. Maybe it is in XML? Or maybe I'm just wrong. `<--bar>` also isn't valid, as far as I know - at least when I test it, it parses as text rather than a start tag.
> but a.-foo is a valid custom element name
That's fine, you can theoretically do all sorts of weird stuff that conflicts with selector syntax; you just have to escape the problematic characters to actually select them. `a\2e -foo` is how you'd spell that element name in a selector.
The problem overall, tho, isn't whether HTML's rules for element names allow or disallow certain patterns; it's that any such rule we'd make for telling "type selector" apart from "concatenation to parent selector" will be heuristic and thus fallible. It can easily fail in HTML itself (see `foo__ { &bar {color: red;}}`), and since CSS and selectors are theoretically usable more widely than HTML, it can fail in exotic and new ways in other host languages too.
--
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6682#issuecomment-928476733 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 28 September 2021 00:01:58 UTC