It depends on the property, but basically the answer is that you should continue to use versions with a browser prefix. It depends on the implementation status and the actual use of different versions of browsers, and not on the standardization status as such.
Check the MDN property descriptions , section Browser Compatibility. Although they are not authoritative and not entirely relevant in all cases, they are an excellent reference. For example, border-radius description says that Firefox 4.0 and later, Chrome 4.0 and Safari 5.0 support a standard, non-prefix version. Older versions have very low usage.
Existing code, on the other hand, should not be flushed. You wonβt win anything, but you risk making stupid mistakes when editing code. Although, for example, in the current version, Firefox ignores the name of the prefixed property, this does not interfere with the pages using it, provided that they also set the property using the standard name.
In contrast, for example, the very useful hyphens feature currently has no support other than a browser prefix. To take another example, border-image is basically only supported as a browser prefix, although Firefox 15 and later and Opera also support the standard name.
There are reasons why older browsers can still be used. One reason is that some applications that are important in some environments may not work in newer versions of the browser. (Or is this what I was told when I came across some very old versions to use.)
source share