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

 I think this is great. The discussion points give me some concern and are
 definitely things we need to discuss.

 Patching from core.svn is still something we "allow." I would have to run
 some queries to see how often patches come from one versus the other. A
 proper Git mirror is in place now for develop.svn, which means that angle
 is less of a concern, at least. We would need to make it more prominent,
 as right now a lot of documentation has still not caught up.

 We haven't really gotten to the point where he develop repo is "runnable"
 in production. Does anyone auto-deploy develop.svnthe way you might do so
 on your auto-svn-updated site? I still use core.svn on mine. So
 develop.svn is a higher barrier to entry.

 Only working on "build" means that even a pretty good way to run and test
 WordPress, outside of "src/", would become more difficult to use. Right
 now all you lose is color schemes and RTL, and of course SCRIPT_DEBUG is
 forced. Making UI and design "choppy" in src/ is not something I'll enjoy.
 (I for one develop in src/ primarily, unless I'm doing front-end work.)

 I think a good first step (as in, we can do it *today*) would be to use
 autoprefixer as a development tool, not a build tool. So we have it
 directly prefix src/. This would have to be done on pre-commit. It can
 optionally be included in patches. A run of `grunt` would expose any
 problems before commit. If a committer misses it, it's not a big deal. We
 can add a test to make sure it runs "clean" (without modifying files).
 Drawbacks are plenty, but it does take the guess-work and extra thought
 required out of auto-prefixing for the time being, and then we can figure
 out where it fits into our build workflow soon.

 ----

 Versions to consider: whether we support a few more versions back in FF
 and whether we support the old branch of a Opera. Also, do we care about
 old mobile Safari? Autoprefixer has a > 1% option, we should at least
 include whatever's in that.

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