Closed greenkeeper[bot] closed 6 years ago
Update to this version instead đ
Autoprefixer 8.3 adds @media
support for grid-template
and fixes gradient direction warning.
@evgeny-petukhov continues his great work for Grid Layout support in Autoprefixer.
Now he improved @media
support. Now this CSS will work in IE:
body {
grid-template:
[header-left] "head head" 30px [header-right]
[main-left] "nav main" 1fr [main-right]
[footer-left] "nav foot" 30px [footer-right]
/ 120px repeat(4, 250px 10px);
}
header {
grid-area: head;
}
main {
grid-area: main;
}
footer {
grid-area: footer;
}
@media (min-width: 1000px) {
body {
grid-template:
[header-left] "head" 30px [header-right]
[main-left] "main" 1fr [main-right]
[footer-left] "footer" 30px [footer-right]
/ 1fr;
}
}
Donât forget that Autoprefixer inserts Grid Layout prefixes only if you set grid: true
option.
@radium-v found that Autoprefixer show warning even if cover
is outside of radial-gradient
.
a {
background: radial-gradient(#fff, transparent) 0 0 / cover no-repeat #f0f;
}
@kotfire improve old direction detection and fix this issue.
Update to this version instead đ
Autoprefixer 8.4 brings new control comment to ignore next line.
@vostrik implemented the @levin-duâs idea of having control comment to disable only next property/rule:
.logo {
/* autoprefixer: ignore next */
user-select: none; /* â ignored */
mask: url(mask.jpg); /* â will be prefixed */
}
/* autoprefixer: ignore next */
::placholder /* â ignored */ {
text-decoration-style: dotted; /* â will be prefixed */
}
Update to this version instead đ
Update to this version instead đ
Autoprefixer 8.5 brings grid-gap
support and fix radial-gradient
direction converting.
@evgeny-petukhov continues his amazing work of adding CSS Grid Layout support to Autoprefixer.
Now he brought grid-gap
. It is amazing work since IE 11 has gaps support in -ms-
grids.
To add grid-gap
support for IE 11 Autoprefixer adds addition grid cells. Unfortunately, it will work only if you have grid-template
in the same rule with grid-gap
. We had a big discussion with a community about these limits.
.a-shortcut {
grid-gap: 33px;
-ms-grid-rows: 1fr 33px minmax(100px, 1fr) 33px 2fr;
-ms-grid-columns: 1fr 33px 100px 33px 1fr;
grid-template:
"head head head" 1fr
"nav main main" minmax(100px, 1fr)
"nav foot foot" 2fr /
1fr 100px 1fr;
}
Old gradients with prefixes used a different direction syntax. Autoprefixer converts direction to old syntax (or warn you to rewrite direction from old to new syntax).
But it has an issue with extent keywords like circle closest-corner
. @BaliBalo reported it and 8.5 fixed it:
.mask {
-webkit-mask-image: -webkit-radial-gradient(100% 50%, circle closest-corner, black, white);
mask-image: radial-gradient(circle closest-corner at 100% 50%, black, white);
}
Update to this version instead đ
-webkit-fill-available
.Update to this version instead đ
Autoprefixer 8.6 brings gap
property support and two values support for grid-gap
/gap
.
CSSWG renamed grid-gap
property to gap
.
@yepninja added gap
support with 2 values support.
Grid layout code bellow will work even in IE if you pass grid: true
option to Autoprefixer:
.main {
gap: 10px 20px;
grid-template-columns: 1fr 1fr 1fr;
grid-template-areas: "head head head"
"nav main main"
"nav foot foot";
}
ignoreUnknownVersions
option for BrowserslistUpdate to this version instead đ
grid-template
with media queries (by @yepninja)Update to this version instead đ
@media
(by @yepninja).Update to this version instead đ
grid
option for grid properties in autoprefixer --info
.Update to this version instead đ
stretch
prefix in Chrome >= 46.Update to this version instead đ
Update to this version instead đ
Autoprefixer 9.0 brings Browserslist 4.0 and drops Node.js 4 support.
We removed Node.js 4 and Node.js 9 support since it doesnât have security updates anymore.
We removed IE and âdeadâ browsers (without security updates) from Babelâs targets:
last 2 version
not dead
not Explorer 11
not ExplorerMobile 11
node 10
node 8
node 6
Autoprefixer Rails 9.0 dropped the RubyRacer and Sprockets 3 support.
Autoprefixer 9.0 uses Browserslist 4.0 to get your target browsers.
Now you use Browserslist to specify Node.js versions. Babel 7 will use Browserslist config as well.
Also, Browserslist 4.0 will warn you if you didnât update Can I Use DB for last than 6 month.
Autoprefixer 9.0 uses PostCSS 7.0
Update to this version instead đ
Update to this version instead đ
Update to this version instead đ
Autoprefixer 9.1 brings background-clip: text
and fix span
in IE Grid.
background-clip: text
beome to be the standard and got Edge support. So we added it to Autoprefixer:
.title {
background: linear-gradient(yellow, red);
-webkit-background-clip: text;
background-clip: text;
}
Note, that Edge expect -webkit-
prefix for this property.
@bogdan0083 fixed an issue when media-query override some grid-template
.
Update to this version instead đ
grid-gap
through @media
(by @bogdan0083).grid-template
and @media
(by @bogdan0083).span X
Grid prefix (by @@bogdan0083).
âď¸ Greenkeeperâs updated Terms of Service will come into effect on April 6th, 2018.
Version 8.2.0 of autoprefixer was just published.
The version 8.2.0 is not covered by your current version range.
If you donât accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of autoprefixer.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you donât have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
8.2 âAd Astra per AsperaâAutoprefixer 8.2 brings [
color-adjust
] support.@YozhikM, @soul-wish, and @yuriyalekseyev did a great work. They added new data to Can I Use and implemented a new feature in Autoprefixer.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donât help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: