[wp-trac] [WordPress Trac] #27078: Use Autoprefixer for CSS vendor prefixes
WordPress Trac
noreply at wordpress.org
Wed Feb 12 15:03:31 UTC 2014
#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 ocean90):
Replying to [comment:2 nacin]:
> We haven't really gotten to the point where he develop repo is
"runnable" in production.
Which I think isn't a real problem. Why should a develop branch be used in
a production environment. Therefore we have our builds.
> 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.
That would be a minimum. But it also means that we have to ignore colors
for now.
> 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.
I'm fine with supporting FF >= 17 and Opera = 12.1. Opera 15 is the first
with Blink, so more or less the same as Chrome. Mobile Safari would be
iOS. What is old here? For the percentages take a look at
http://caniuse.com/usage_table.php or
https://github.com/ai/autoprefixer/blob/master/data/browsers.coffee. The
`> 1%` option wouldn't make a difference with our values.
----
Replying to [comment:4 jorbin]:
> One possible solution to the problem of keeping src running pretty would
be to use http://leaverou.github.io/prefixfree/ only in the src directory.
Would be an idea, but I think we should try to avoid to bundle another JS
lib. Haven't tested the performance yet, but does it work with many (and
huge) stylesheets?
----
Replying to [comment:5 nacin]:
> I wouldn't mind eventually abandoning core.svn as a place to patch from,
but I don't think holding out for a little while longer is a bad thing.
Would be nice to know how many patches are still coming through core.svn.
Abandoning core.svn will make things easier - now and in future.
Replying to [comment:6 wonderboymusic]:
> I would much rather we go all-in and use Compass.
As much I liked Compass in the past I don't want it back. It adds to many
mixins and functions which we will not use in cure. And as iskin mentions,
Compass adds a lot of unnecessary prefixes.
> back-compat-needing properties like `opacity`.
These properties are just hacks in my eyes. Autoprefixer doesn't care
about this - which is great, since it's not a prefix, it's a proprietary
property.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/27078#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list