3
I was taking a look at the prefixes and with a lot of code to put them (I didn’t have the habit of using the prefixes until I started using the new properties of CSS, sad) and went to take a look at online tools to do the hard work.
I found this site very interesting: http://pleeease.io/play/. When I put some properties like the transform:translate(-50%, -50%), he only puts two prefixes: -webkit- and -ms-. I realized that prefixes are really important when the Transform only worked in IE with them, but I want to know why the tool does not include all prefixes.
They vary from property to property?
When a property is not yet 100% standardized, but suppliers of browsers want to include it immediately, without waiting for the end of the standardization, they usually use a proper prefix (
-webkit-,-moz-,-ms-,-o-, ...) to - if the property changes in the future - not break old code that already used it as it was implemented (I think). As the standardization is completed, the prefix becomes unnecessary, as the browser accepts the standard version as well, without the prefix (it is already implemented in accordance with the final specification).– mgibsonbr
I had read about it while researching, it’s a very interesting thing to know. That must have been what happened to the
border-radius, before some browsers did not display without the prefix, now it has standardized. I will put the new properties with all prefixes :)– Rafael Almeida