-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[css-grid] translate grid
property syntax into IE safe syntax when possible
#1023
Comments
What is your current output? |
It doesn't attempt to translate it at all. The output is just what I wrote in. /* what autoprefixer outputs even if the grid setting is turned on */
.grid {
display: -ms-grid;
display: grid;
grid: "left .... right" 100px /
1fr 10px 1fr;
}
.left-cell {
grid-area: left;
}
.right-cell {
grid-area: right;
} |
Do you set |
Yes, notice that the output did translate the I'm using autoprefixer v8.3.0 |
Hm. I will look later on this week. |
It's true. We don't support |
That's why I added "when possible" into the title of the issue. I had a feeling there would be aspects of the I would love it if autoprefixer was able to detect if the syntax is possible to replicate in IE and if so, create the IE equivalent css. If it isn't possible to replicate then autoprefixer can ignore the Once you know the I was so happy when autoprefixer started supporting grid area syntax. It makes working with grid in IE so much easier. Supporting the |
I only just found out that I haven't tested it yet. If autoprefixer can translate |
@Dan503 You are damn right! Your case is definitely the case of
And of course, you want that these properties work in IE (that why we are here). So if you use |
Ok I think under that reasoning it is probably a good thing that autoprefixer doesn’t support
It's a bit easier than using @ supports statements. If autoprefixer is able to translate |
The links are coming up as 404 pages for me :/ |
Derp. Fixed. |
Cool. I'll close the issue :) |
This code
Should translate into this:
The text was updated successfully, but these errors were encountered: