- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Aug 2022 20:23:23 +0000
- To: public-css-archive@w3.org
> There is no clear signal to stylesheet authors that `@supports (gap: 1px)` will sometimes be true when they would expect it to be false. Yes, authors still need to learn about this context relation and CSS itself cannot change this, unfortunately. So this issue focuses on a way to at least make it _possible_ to detect context related support of features. As @tabatkins [pointed out earlier](https://github.com/w3c/csswg-drafts/issues/3559#issuecomment-458734231), user agent creators want to avoid a situation in which they have to maintain a table of context relations. Custom `@support` checks take away that burden from them and still provide authors with the possibility to check for context related support. > Linters/build tools could warn when they encounter ambiguous `@supports` rules to help stylesheet authors. That's definitely true. And I am pretty sure that some of them already do that. But that's out of scope of the specifications, of course. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3559#issuecomment-1224817154 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 23 August 2022 20:23:25 UTC