- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Sat, 23 Dec 2023 01:48:55 +0000
- To: public-css-archive@w3.org
I think @tabatkins's https://github.com/w3c/csswg-drafts/issues/3559#issuecomment-458734231 (which I agree with) was a good explanation of why we *don't* want a general solution here.
However, I think it might be reasonable to add specific, one-off solutions when we think they're important enough. They'd need to be for significant enough features that we'd be willing to add an extra keyword to CSS for them, and that an implementor wouldn't miss that it needed to be implemented, and that we'd be willing to write specific web-platform-tests to verify and monitor the results closely to make sure the rollout doesn't go wrong. And we could probably choose reasonably verbose keywords.
For example, for the two examples discussed recently we could add something like `gap-on-display-flex` or `align-justify-properties-on-blocks` keywords so that it would be possible to write:
```css
@supports feature(gap-on-display-flex) {
/* ... styles ... */
}
```
(It's likely too later for the former to be useful at this point, but the latter is something we really could consider now.)
--
GitHub Notification of comment by dbaron
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3559#issuecomment-1868169502 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 23 December 2023 01:48:57 UTC