remove -ms- prefixes for particular IE10 features

[paulirish]

based on http://blogs.msdn.com/b/ie/archive/2012/06/06/moving-the-stable-web-forward-in-ie10-release-preview.aspx

we don't need ms prefixes on transitions, gradients, or keyframe animations. let's strip them out.

[alanhogan]

Nice :)

I absolutely love that Compass users have these decisions made for them for free. +1

[alanhogan]

Also, big ups to MS for helping battle excessive prefixing here.

[chriseppstein]

@paulirish Was there never a shipped version of IE that had these prefixed then?

[paulirish]

Was there never a shipped version of IE that had these prefixed then?

Nope. Just IE10 platform previews.

IE9 has prefixed transforms (and IE10 will not) so we're stuck with -ms-transform for a while

[chriseppstein]

Fixed. Thanks for the heads up!

[salimhb]

For people who might be puzzled when linear-gradient doesn't work in IE10 in some cases without adding the -ms prefix, read this: http://joshuapaling.com/post/compass-background-gradients-not-working-ie10

[vote539]

I use Compass to simplify my coding process on faith that it is covering all important edge cases. However, after going to my newest site on a friend's PC, I discovered that the background gradients are completely messed up in IE 10.

Do you think we can reverse this commit and add the -ms- prefix back into Compass gradients? The -ms- browser prefix increases the weight of CSS no more than the -o- browser prefix, and yet it reaches a much larger audience.

[salimhb]

@vote539 there's no need for the ms- prefix, check the link I posted in my previous comment.

[vote539]

I read your link yesterday. What I'm saying here is something different.

I understand that the objective of Compass is to ease development by making CSS statements cross-browser-compatible when possible. The fact that I can write a SASS linear-gradient statement that works in WebKit and Gecko but not IE 10, despite the fact that the documentation for that function claims to support IE 10, is a problem.

If I had not used Compass in my project and instead used one of the CSS gradient generators available online, my site would have worked in IE 10 from the start. That's also a problem.

I think it's great that IE 10 supports the W3C standard linear-gradient without a prefix. However, Compass should either always output linear-gradient statements that are compatible with IE, or it should output the -ms- prefix to increase compatibility.

[salimhb]

In my case, Solution 1 from that link worked, but Solution 4 seems to cover all cases, have you tried it?
The thing is that the problem here is about the parameters passed to linear-gradient, not the support for linear-gradient itself.

[vote539]

My site uses a limited number of left-to-write gradients, so Solution 1 won't work for me. I ended up using Solution 3. But that's not my point. I can always find workarounds. If Compass is supposed to make my life easier, it should prevent me from ever needing to read that article.