Error - Unknown @ rule: @-ms-keyframes

[diggabyte]

Introduced after this commit:
e14628b

Looks like the @-ms-keyframes prefix was accidentally overwritten with @-o-keyframes when fixing issue #286

I commented on the line that broke it.

[diggabyte]

Here is the line that broke it:

e14628b#L0L5559

[nzakas]

This is intentional. Microsoft has unprefixed keyframes for IE 10 and will no longer use the prefixed version. See:
http://blogs.msdn.com/b/ie/archive/2012/06/06/moving-the-stable-web-forward-in-ie10-release-preview.aspx

[diggabyte]

I see. What about backwards compatibility for versions of IE < 10? Similar to how prefix warnings are output for legacy -moz, etc.

[nzakas]

IE 10 is the first IE to support CSS animations.

[Bart76]

Closed? Strange. And Diggabyte's just question about backward compatibility remains completely unanswered... (Or is "stupidly neglected" perhaps a better term in this specific case?)

I just noticed that - after more than six years - this issue is still topical. I am confident that the CssLint behavior is incorrect. As I see it, a specific browser version has NOTHING to do with correct (historical) CSS analysis.

Or perhaps should I understand that targeting and using earlier versions of IE should not be taken seriously anymore? (Nowadays, that might be a fair subject of discussion, but six years ago when IE10 was just released?...)

And during the last six years, everybody who is/was related to the CssLint project seemed to pretend that this is quite fine. Otherwise, Diggabyte's question would have been satisfactory answered.

Seems that quality goes down the toilet on purpose here. Madness. Good luck with this project.