- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Mar 2024 22:43:40 +0000
- To: public-css-archive@w3.org
Yeah, I think way too much weight is being assigned to some of the items I listed here : https://github.com/w3c/csswg-drafts/issues/10001#issuecomment-1978136727 :) In particular `people new to CSS will have a hard time learning the difference between this and the universal selector` That statement assumes that there **is** a perceived difference for CSS authors. If however they appear to work the same, then that entire item becomes irrelevant. My concern here was that there would be a set of rules and behaviors for universal selectors and a different set for wildcards. If they align, then this is moot. ---------- As I finished that comment, I am actually in favor of figuring out how to make `*` work. But I also don't think the feature stands or falls with this exact syntax :) ----------- > Also, whether beginners can understand the difference between .foo-* and .foo- * is a pretty easily testable hypothesis. 😄 Yup, easily testable :) But only relevant if there is an actual difference. As you also say, `*` is a widely understood concept and for authors `*` might just mean "expand" the current selector to any matching element. -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10001#issuecomment-2008287934 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 March 2024 22:43:41 UTC