[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 helen):

 As far as running out of src (which I do for the vast majority of core
 dev, FWIW) and back-compat and all this Compass talk:

 * If a property is still required to be prefixed for use in any browser,
 we should be judicious about it, as it should be considered experimental
 and subject to change. I'd actually question if we should really be using
 it at all, given that being newest-and-shiniest is not our top priority
 (saying this knowing that 3.8 introduced a good amount of these). So, in
 those cases, we should be maintaining them by hand, and they should
 gracefully degrade, anyway. A pre- or post-processor should not play a
 part in their usage. This means that using a modern browser should give
 you the final experience when running out of src.
 * In cases like opacity, we should not be attempting to make the
 particular browser(s) that need that "back compat" match. If something
 doesn't degrade gracefully, we need to fix the issue, not the tooling.
 * Compass is beyond overkill, I am not a fan for the reasons listed above,
 I am not yet convinced of its longevity, and I still have yet to come to
 believe that a pre-processor is the right choice for the WordPress
 project.

 Also, ocean90 - I'm not sure I totally understand why it has to run after
 minification - why not just before?

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