Vendor Prefixes, the short solution.
Posted on by Sheerman
- Developers: Carry on doing your job properly. If you’re using experimental features, prefix them, if the browser vendors have bothered to implement that feature.
- Browser Vendors: Carry on doing your job properly. If you want developers to make websites look pretty in your browser, work to give them vendor prefixes for experimental features, and shout about them, so everyone knows you’re awesome. When the specs are finalised, implement them.
- W3C: Carry on doing your job properly. Look at all the lovely new things people are using, and work to finalise them so browsers can ditch the prefixes, and developers don’t have to worry.
Was that so hard? Any questions? Are we all good? Good.
Couldn’t agree more. I’ve heard too many arguments against prefixes. Arguments stating that you’re “KIlling Kittens” if you use them and that the W3C should dictate everything. The tail shouldn’t wag the dog as some suggest.
Use the Less Framework and hopefully we can link out to a file where someone/thing updates with latest vendor prefixes. This is a good start…lesselements.com/
But don’t use it out of the box. Last update was a year ago … check which prefixes for firefox (paulrouget.com/e/unprefixing-in-firefox-16/) and webkit browsers are still necessary and where the opera prefix is actually required as it is missing a lot …
even though many will be unprefixed with the next version my.opera.com/ODIN/blog/whats-new-in-opera-12-10-beta
Yes Dan! Excellent.
apropos lazy developers: the Chrome crowd (which is to some extend similar to the IE crowd 12 years ago IMO) forces Opera – as a browser with a smaller user and developer base to this:
my.opera.com/ODIN/blog/2012/08/10/css-vendor-prefixes-in-opera-12-50-snapshots