- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Nov 2024 15:44:37 +0000
- To: public-css-archive@w3.org
Do note that many component libraries need rules to avoid FOUC. Currently, these look like this:
```css
:where(:not(:defined)),
:where(:not(:defined)) * {
opacity: 0;
}
```
This would target _any_ element on the page that is not defined (including elements that were never _meant_ to be defined), because it is *impossible* to target those that actually belong to the library (i.e. have a shared prefix).
I think wildcard matching is incredibly important for a number of use cases. I would personally prefer to fit it into the existing syntax so that it can be added across a variety of syntax without expanding the API surface (e.g. `foo-*` for elements, `.foo-*` for classes, `[foo-*]` for attribute names and so on) but the important thing is making it _possible_ at all, even with awkward pseudo-class syntax...
--
GitHub Notification of comment by LeaVerou
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6571#issuecomment-2457518124 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 5 November 2024 15:44:38 UTC