Dan Tonon

Recognise that this is just an edge case. I'm not endorsing the removal of the warning all together. Only for this particular scenario. The warning can be worked around by...

I've never really had an issue with that. Browser support for the new style of media queries (the ones with greater and less than symbols) isn't good enough to rely...

That's an ok temporary solution. The advantage of having Autoprefixer understand `@supports` though is that you can still get prefixing on values not associated with the `@supports` statement inside `@supports`.

Yes it should disable prefixing but only for properties associated with the `@supports` statement. ```css @supports (display: grid) { display: grid; /* should not get prefixed */ user-select: none; /*...

No, that's not what this issue is. From the screenshot you sent, it's hard to tell why IE would be doing that. Are you using `auto` to size the columns...

@cloudsociety that isn't what this issue is about. Can you please open a seperate issue?

This issue is about the fact that Autoprefixer is currently outputting prefixes for code that is impossible for it to prefix safely. ``` grid-column-start: span 6; ``` This is impossible...

[css-grid] Autoprefixer outputting unsafe IE [column/row] [end/span] syntax

Nevermind, in desktop view I can do it myself.

We need a bit more to go off. Can you post a code example? Mixins don't exist in CSS and Autoprefixer doesn't read Sass source files. It is most likely...