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

 > I still have yet to come to believe that a pre-processor is the right
 choice for the WordPress project.

 ... This is tricky, because depending on who you ask, the answer would
 range from "YES" to "ABSOLUTELY NOT."

 In the end, what any project wants is minified CSS file that will load
 fast when gzip gets involved. Also, what any project wants is modular
 code.

 *I* (me, my opinion) would be yes, let's go full-bore - I don't feel like
 1) we get a huge wave of CSS patches and 2) when we do, it wouldn't be
 horrendous if the noob provided 17 lines of CSS that one had to convert
 into Saaaaassssy CSS code. 90% of the PHP patches are stale in Trac right
 now, and will require being rewritten. 99.9% probably have weird white
 space that needs fixing.

 It's funny that everyone is hating on Compass, because that was one of the
 selling points of SASS over LESS. (I continue to prefer LESS.) Even if
 Compass or "unnamed tool" is overkill, it's not used in prod, so shouldn't
 matter. Any random node module will require dozens of dependencies.

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