[wp-trac] [WordPress Trac] #27078: Use Autoprefixer for CSS vendor prefixes

[WordPress Trac]

#27078: Use Autoprefixer for CSS vendor prefixes
------------------------------+------------------
 Reporter:  ocean90           |       Owner:
     Type:  task (blessed)    |      Status:  new
 Priority:  normal            |   Milestone:  3.9
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  has-patch         |     Focuses:
------------------------------+------------------

Comment (by iskin):

 Note, that Compass had no stable releases for a more that year:
 http://rubygems.org/gems/compass/versions

 It generate a lot of unnecessary prefixes. For example, border-radius
 doean’t need prefixes: http://caniuse.com/border-radius
 When Fotorama was moved from Compass it save 10 % of their CSS:
 https://twitter.com/fotoramajs/status/362686759944982528

 Also, it doesn’t support a lot of prefixes. No @keyframes prefixes in
 stable release. No prefixes for selectors. No prefixes for calc()
 function.

 But @wonderboymusic is right, Autoprefixer is only about prefixes and
 backward compatible is very different task (BTW, opacity never need
 prefixes). But you can use Compass for compatible tasks and Autoprefixer
 will clean it outdated prefixes and add prefixes, that it doesn’t support.

 But I think, best solution is to add own mixins for backward compatible,
 because most of IE hacks is very slow (and old IEs are used on very old
 PC) and in every case we need to think, does this feature is required or
 we can use graceful degradation (like in border radius, gradients).

--
Ticket URL: <https://core.trac.wordpress.org/ticket/27078#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform