- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 Aug 2022 17:35:40 +0000
- To: public-css-archive@w3.org
> In the case of flex gap specifically, is there any workaround for web developers to detect support for it? It's only recently shipped in Chrome and even more recently landed in Safari Technology Preview, and without feature detection people will need to wait for another 3 years or so to be able to simply assume it will work.
Much longer than this :/
2 years have past since this statement and we still do not allow `gap` at all because we can not write fallbacks. We typically support 5-8 years of browser versions.
If `@supports (flex-gap: 1px) {}` was available in the next version of each browser we could start using it.
We don't care that there are some versions with native support that would get the fallback.
We do care about the browsers without native support.
--
GitHub Notification of comment by romainmenke
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3559#issuecomment-1220924140 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 19 August 2022 17:35:42 UTC