Lots of exciting new features have been landing in CSS recently, and it can be tough trying to figure out if they’re safe to use or not. We might know that a feature is available for 92% of users, but is that sufficient? Where do we draw the line? In this blog post, I’ll share the framework I use for deciding whether or not to use a modern CSS feature
Frontend
Source：https://www.joshwcomeau.com/css/browser-support/
A Framework for Evaluating Browser Support
Josh Comeau0 views
PreviousNext-level frosted glass with backdrop-filterNextA Friendly Introduction to Container Queries
Related posts
How I Built a Data-Driven Portfolio That Takes 30 Seconds to Update
0HackerNoon
Building a Typography Playground With Variable Fonts and Fluid CSS
0HackerNoon
The accessibility engine was already in our node_modules, reached by a linter that cannot run
0dev.to
How I built true background step counting in React 19.2 + Capacitor on Android 14/15 (without Google Fit, which is shutting down)
0dev.to
Creator commission is a cash event, not a percentage
0dev.to
Every one of our 79 pages is two clicks from the homepage, and 24 of them cannot be reached by reading
0dev.to