The box might look prettier with a shadow, but lack of box-shadow isn’t going to obscure its content. And same as before: this is a progressive enhancement. This is the exact same issue as above: there are more older browsers that need prefixes for box-shadow than for border-radius, but it’s still only half a percent. I’ve never seen a website become unreadable or inaccessible when border-radius was removed. By now, the best thing to do is consider border-radius to be a progressive enhancement. Chances are, you’ve written at least one of those browser off as “unsupported.” You’ve got more than 10x as many IE8 users as you have border-radius prefix users. Before replying with lofty ideals about “no user left behind,” think about what you do for IE6-8. Firefox 3.6 & down, Chrome 3 & down, Safari 4 & down, iOS 3.2 & down need border-radius prefixes. 26%: that’s the total global browser usage that needs a prefix on border-radius. Let’s look at the mixins you should stop using right now: Border-Radius Prefixes # I’m talking about worthless mixins that bloat CSS and serve no one. I’m not talking about the cool proof-of-concept “let’s create an icosidodecahedron with CSS” mixins – those have their place. One of the most common ways people misuse Sass is creating mixins that they never needed in the first place. Is a powerful tool – this power makes it easy to misuse.
0 Comments
Leave a Reply. |