Autoprefixer 6.2 contains spec changes, text-emphasis-position
, better @support
and linear gradients support.
Spec Changes
W3C changed fill-available
to fill
in Intrinsic & Extrinsic spec. @yisibl found it and updated Autoprefixer behaviour.
Autoprefixer will warn you about outdated fill-available
in your CSS, but it will not fix it for you. Because your CSS should be ready for the prefix-less future.
Transition
Autoprefixer just works: you can write any CSS and Autoprefixer does the rest (even with complicated cases). But now we have the case when Autoprefixer retreats.
Look at this output for transition-property: color, filter
:
a {
-webkit-transition-property: color, -webkit-filter; /* UC Browser */
transition-property: color, -webkit-filter; /* Safari */
transition-property: color, filter; /* Future version of Safari */
transition-property: color, filter, -webkit-filter; /* Blink and other browsers */
}
As you can see, we need to change amount of properties for a different browser. Unfortunately, we have cases, when Autoprefixer can break a CSS:
a {
transition-property: color, filter;
transition-duration: 600ms, 300ms;
}
.is-slow {
transition-duration: 1200ms, 600ms;
}
Sorry, but I didn’t find a solution for this case. Autoprefixer will show the warning and force you to use multiple names only in safer transition
instead of transition-*
.
Supports At-Rule
In 6.2 we rewrote all code for @supports
at-rule:
- Now Autoprefixer adds prefixes to parameters only for browsers with
@supports
support. - With new brackets parser we solved broken parenthesis in some cases found by @kmuncie and @heady.
Time Capsule
We put a “time capsule” into Autoprefixer so that we are ready for the prefix-less future. If Autoprefixer sees, that your specified browsers
don’t require any prefixes, it will ask to delete itself.