How much browser support is enough?

[@OPPATRIA]

My problem is that I probably haven't fully understood @layer yet. I'm currently having to work with a creepy css framework, KENDO. It's full of importants, and I thought I'd encapsulate all that in a @layer so afterwards I can write my adjustments and extensions in peace. I thought: reset, kendo, my-custom-extensions - but then everything was messed up. Whatever. But yes, my motto: after 24 months you're actually safe with new stuff, and for ESR browsers you try graceful degradation.

[@armornick]

I'm not a professional CSS developer (yet) but for my personal projects I generally don't use a feature until it's supported in Chromium, Firefox and Safari.

[@ico0z]

For me it's not only to look for "The 99% support or does all the major browser support it" I generally will consider a support with a history with a lot version behind the feature release

[@hoshi411]

1 ) the absolute worst browser in keeping up with web standards is iOS safari and mac safari follows close behind that. 2 ) at least half of the people use safari Conclusion: People who know, know. If you don't code for safari first, you will pay later. I also passionately hate safari.

[@eksperiment6269]

I might be in the extreme in some peoples opinion, but for me I'm ready to implement at around 88%. I think for too long the general consensus has been to hold back on new technologies for too long and that it has slowed down development, but now my philosophy is to implement new technologies early and say that it is the users responsibility to keep their browser up to date.