Vendor prefixes inside keyframes cause false 'missing standard property' error

[k88hudson]

Looks like vendor prefixes inside keyframes cause the 'missing standard property' error to fire.

Code:

@-moz-keyframes spin{
    0%{ -moz-transform: rotateX(-10deg) rotateY(0deg); }
    100%{ -moz-transform: rotateX(-10deg) rotateY(-360deg); }
}
@-webkit-keyframes spin{
    0%{ -webkit-transform: rotateX(-10deg) rotateY(0deg); }
    100%{ -webkit-transform: rotateX(-10deg) rotateY(-360deg); }
}
@-o-keyframes spin{
    0%{ -o-transform: rotateX(-10deg) rotateY(0deg); }
    100%{ -o-transform: rotateX(-10deg) rotateY(-360deg); }
}
@-ms-keyframes spin{
    0%{ -ms-transform: rotateX(-10deg) rotateY(0deg); }
    100%{ -ms-transform: rotateX(-10deg) rotateY(-360deg); }
}
@keyframes spin{
    0%{ transform: rotateX(-10deg) rotateY(0deg); }
    100%{ transform: rotateX(-10deg) rotateY(-360deg); }
}

Error:

line 5, col 9, Error - Missing standard property 'transform' to go along with '-moz-transform'.
line 6, col 11, Error - Missing standard property 'transform' to go along with '-moz-transform'.
line 9, col 9, Error - Missing standard property 'transform' to go along with '-webkit-transform'.
line 10, col 11, Error - Missing standard property 'transform' to go along with '-webkit-transform'.
line 12, col 1, Error - Unknown @ rule: @-o-keyframes.
line 17, col 9, Error - Missing standard property 'transform' to go along with '-ms-transform'.
line 18, col 11, Error - Missing standard property 'transform' to go along with '-ms-transform'.

[fi5er]

Possible regression?
I'm still seeing this issue with CSSLint 0.10.0 (the most up-to-date version on npmjs.org).
According to the change log, the fix should be included since version 0.9.9.

[jasonrhodes]

I'm also seeing this exact error showing up in 0.10.0, specifically because (as the example above seems to also indiciate) I'm using Font Awesome's drop in SASS files and they include this @keyframes spin situation that demonstrates the problem perfectly.

[mtscout6]

I'm also running into this problem on version 0.10.0, I'm using Font Awesome's drop in Less files. Have you figured out a solution for this?

[bjankord]

I'm still seeing this issue with CSSLint 0.10.0