Paul Irish on Chrome Moving to Blink

I know you’ve been asked this plenty of times already, but: no new vendor prefixes, right? Right? Nope, none! They’re great in theory but turns out they fail in practice, so we’re joining Mozilla and the W3C CSS WG and moving away them. There’s a few parts to this. Firstly, we won’t be migrating the existing -webkit- prefixed properties to a -chrome- or -blink- prefix, that’d just make extra work for everyone. Secondly, we inherited some existing properties that are prefixed. Some, like -webkit-transform , are standards track and we work with the CSS WG to move ahead those standards while we fix any remaining issues in our implementation and we’ll unprefix them when they’re ready. Others, like -webkit-box-reflect are not standards track and we’ll bring them to standards bodies or responsibly deprecate these on a case-by-case basis. Lastly, we’re not introducing any new CSS properties behind a prefix. Pinky swear? Totes. New stuff will be available to experiment with behind ...

adobe ambitions android apple applications blink-powered canary chris chrome chromebook chromeos chromium coffeescript commitment compatibility confirmation conformance css darin dart decision deprecation dev development devtools divergence dom emscripten expectations experience experiment firstly fisher freedom google haha implementation integration interoperability ios irish javascript javascriptcore lastly limitations linux mac maintenance management mention mozilla non-webkit nope oilpan opera paul performance pinky policy practice priority quality rangeexception recalculation resistance safari scalability secondly simplicity technology tradition typescript vbscript-y version webkit webkit-based wilson windows xmlhttprequestexception