- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Apr 2021 17:28:14 +0000
- To: public-css-archive@w3.org
Yeah, my original intention was that they should be the same - they both use Kleene 3-value boolean logic, where "unknown" negates to "unknown", and if the whole thing evaluates to "unknown" it is treated as false. But I see the logic in treating an @supports unknown as just plain false, because the supports queries aren't nuanced choices from equally-likely options, like MQs are. If you don't understand a supports condition, it's likely you don't understand the feature it's testing support for either. (That can be wrong, but it's much more likely to be right than not.) So yeah, it's much more likely to give a correct result if it's just a plain false. So I agree, we should remove the "unknown" value from supports conditions, and just treat unknown things as false. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6175#issuecomment-828639445 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 28 April 2021 17:28:16 UTC