- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Mon, 29 Jan 2024 16:51:11 +0000
- To: public-css-archive@w3.org
> Some generic feature test on the other hand like `@supports (gap: 1px) with (display: flex)` seems more intuitive to me as it describes spot on the query of a problem that needs solving: _does this work in the context of that?_ I think the basic reason not to do this is that there are probably a few thousand different options for the things on either side of the `with` in your proposal (different CSS properties, plus different generations of values added to those properties over time), which means there are a few million possible `with` combinations. There's no ready source of data for the answer to those few millions of questions, so we (both the working group and implementors) would need to sit down and decide what the correct answer to each one is, ensure engines implement them correctly, and test them. If you combine that with the reality that there's a single digit number of these questions that we know are much more interesting than all the others, it seems much more solvable to deal with the single digit number of questions than with a few million questions. -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3559#issuecomment-1915148442 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 29 January 2024 16:51:13 UTC