comment in @keyframes declaration causes ParseError

[mbazaczek]

Hello, I've recently updated less.js in my WinLess complier, only to find that "@-webkit-keyframes hover" declaration now happily throws "ParseError: Unrecognised input".

I am now unable to vendor prefix my @Keyframes declarations.

I didn't found any mention of it in the changelog, so I suppose there is no alternative way of doing it as of 1.7.1.

Plx halp

[seven-phases-max]

Could you please provide a specific code you get the error with? The simplest case compiles as expected:

@-webkit-keyframes hover {
    0%   {color: red}
    100% {color: blue}
}

[mbazaczek]

Thanks for instant response!

You're right - that was not the culprit. Before update, this compiled just fine:

@-webkit-keyframes hover /* Safari and Chrome */{ ..keyframes... }

But as of 1.7.1 it throws ParseError.

I've removed the comments and now it compiles all OK.
Sorry for the inconvenience!

[seven-phases-max]

Ah, I see, thanks! If I'm not mistaken it's a minor regression bug by #1860. Before it was possible to put any arbitrary value (incl. comments) after @keyframes before {, but now it expects only a single identifier or a variable.

[mbazaczek]

Indeed.

I've changed the ticket name to more accurate.

[SomMeri]

Fixed by last commit.