3 ms·
The moment your code begins to look like this -webkit-transform: rotate(-70deg); -moz-transform: rotate(-70deg); -ms-transform: rotate(-70deg);
by pilif 15y ago
The moment your code begins to look like this
-webkit-transform: rotate(-70deg);
-moz-transform: rotate(-70deg);
-ms-transform: rotate(-70deg);
-o-transform: rotate(-70deg);
you know that it's time to either drop the vendor prefix or to hope that there will not be another browser vendor implementing the exact same functionality and again protect it behind a prefix.
I know that technically, the transform specs are not finalized, but considering this kind of consensus (even IE seems to agree), would it even be wise to change the spec again?
- chriscoyier 15y agoI think it's nice to see. It means the spec is probably pretty close to being finalized, because in order for that to happen, there needs to be at least two browser implementations.
- yuhong 15y agoTechnically, browsers are supposed to drop the prefixes when the spec reaches Candidate Recommendation.
- andyford 15y agoThe moment before your code looks like this, you use Sass.
- eneveu 15y agoThe moment your code begins to look like this, you know that it's time to use SASS mixins / Compass :)