@bramus Caveats: Chrome 129+ only. Experimental. Not supported by Safari or Firefox.
https://caniuse.com/mdn-css_properties_interpolate-size_allow-keywords
Top-level
@bramus Caveats: Chrome 129+ only. Experimental. Not supported by Safari or Firefox. https://caniuse.com/mdn-css_properties_interpolate-size_allow-keywords 3 comments
@bramus it does matter in the sense that it won't be supported, and future adoption is uncertain. No, it won't break anything, but it won't work either. This is not an unreasonable thing to mention. Lots of new CSS features are about progressive enhancement. This is not different. It's still important for developers to keep in mind what works and when/where, and what doesn't. The world is not just Chrome/Blink. @zeh These features are part of official CSSWG resolutions and are ready for other vendors to implement. Sometimes Chrome implements something first, and sometimes Chrome is last. Here, Chrome happens to be first. The thing with Progressive Enhancement is that you don’t have to care about what works when or where. You put a solid good working base experience in place that works out of the box. But if the browser supports more than just that base, they get a better experience. |
@zeh As noted in the article the lack of browser support doesn’t really matter here, as it’s a nice progressive enhancement: browsers with no support get the rough switch. Browsers with support (which is Chromium-based ones only at this moment) give you the nice transition.