Last Updated: February 25, 2016
·
2.761K
· moak

Start dropping some -moz prefixes

In the spirit of http://dowebsitesneedtolookexactlythesameineverybrowser.com/

I have stopped including the -moz-border-radius prefix on projects and here is the rationalization:
According to
https://developer.mozilla.org/en-US/docs/CSS/border-radius
border-radius has been supported since FF4

When checking http://en.wikipedia.org/wiki/Firefox for the release history we can see, that FF3.6 was released nearly 3 years ago, FF4 has been available close to 2 years. So Users who have not upgraded their FF in 3 years falls into the ~1% and under category of browsers on the web
See:
http://gs.statcounter.com/#browser_version-ww-monthly-201207-201209
http://www.w3schools.com/browsers/browsers_firefox.asp

Which is almost equal to supporting IE6.

Now some clients want full cross browser support, and they will have to pay for IE6 compatibility, so why not FF3.6 > compatibility?

I'm just throwing it out there that maybe it's time to start embracing CSS3 without certain -moz vendor prefixes. (webkit will probably be a different ball game)

Like if you agree, comment if you disagree :)

PS: Or drop all prefixes and start using a JS script like
http://leaverou.github.com/prefixfree/

PPS: same goes for box-shadow https://developer.mozilla.org/en-US/docs/CSS/box-shadow but not for box-sizing https://developer.mozilla.org/en-US/docs/CSS/box-sizing so research the common -moz prefixes you want to drop and let them go

Have a fresh tip? Share with Coderwall community!

Post
Post a tip
Did you know?

JavaScript on a page runs with the privileges of that origin. One altered library, tag manager, or snippet can read inputs, change what people see, and call your APIs as the user.

Security insights from Cside