Are vendor specific style prefixes needed any more on most common CSS3 properties? [closed]

问题

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.

Closed 7 years ago.

I guess most of us are used to write common CSS3 properties with vendor specific prefixes to support all browsers, so it's not uncommon to see something like this:

border-radius: 6px;
-moz-border-radius: 6px;
-webkit-border-radius: 6px;
-o-border-radius: 6px;

I recently noticed that on most common properties the prefix is not required any more. And given the rapid update cycle of current browsers, I started to think about the necessity of keeping the prefixes - e.g. there probably are not many versions of Chrome still in the wild that do not support the native border-radius syntax.

Also I've always thought of these kind of properties as just eye candy, so I don't think there would be any problem about dropping support for the now obsolete Firefox 3.* and the likes in this regard.

So, is it safe to drop the prefixes on most common properties, namely border-radius and box-shadow?

来源：https://stackoverflow.com/questions/7261208/are-vendor-specific-style-prefixes-needed-any-more-on-most-common-css3-propertie