- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Mon, 22 Aug 2022 20:24:04 +0000
- To: public-css-archive@w3.org
For Houdini features I actually do not mind the tradeoff. The "user story" is straightforward here. _I want to do something browsers normally can't, so I reach for an API which enables custom behaviour._ Custom `@supports` for native properties are a different case in my opinion. It is not intuitive and obvious that a stylesheet authors needs to create a supports worklet and think about the issues listed above when they actually want to use a standard property. ------------ The same however is true for `@supports (flex-gap: 1px)` or `@supports (gap: 1px) in (display: flex)`. There is no clear signal to stylesheet authors that `@supports (gap: 1px)` will sometimes be true when they want it to be false. Linters/build tools could warn when they encounter ambiguous `@supports` rules to help stylesheet authors. -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3559#issuecomment-1222941656 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 22 August 2022 20:24:06 UTC