- From: Marcel Laverdet via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Oct 2023 20:11:06 +0000
- To: public-css-archive@w3.org
I found `inset` approximates support for flex gap pretty well. Compare browser comatibility data between the two: https://developer.mozilla.org/en-US/docs/Web/CSS/gap#browser_compatibility https://developer.mozilla.org/en-US/docs/Web/CSS/inset#browser_compatibility `@supports (inset: 0)` will not target any browsers which don't support flex gap. The `@supports` check will also not target some browsers which *do* support flex gap: Chrome [84, 85, 86], Firefox [63, 64, 65], or Opera [70, 71, 72]. Support in WebKit matches perfectly. If you're using mdn browser compat data to drop polyfills from your stylesheets it works well to avoid bundling clumsy margin-based polyfills. Obviously I would love to see a fix for the underlying standards issue but this is a solution we can use today for the flex case. -- GitHub Notification of comment by laverdet Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3559#issuecomment-1758459996 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 October 2023 20:11:08 UTC