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

SmartInventory
0dev.to
The Prediction Succeeded. The CLI Still Failed.
0dev.to

Rolling Out Passkeys Without Locking Users Out
0dev.to
I built a CLI harness that strips JS/TS function bodies with Babel AST to save 80% context tokens
0dev.to

Vercel UI SDK Beta, Hands On: 91 Behaviors, 4-Second Install, 36 KB per Popup
0dev.to

The progress bar that made typing lag: debugging a 331 ms INP in a React game
0dev.to