Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workaround to fix semicolon syntax issue with keyframes #140

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

arbylee
Copy link

@arbylee arbylee commented Dec 19, 2014

Context: Lessc is adding a semicolon at the end of keyframes definition, which is
invalid css and causes issues on some devices. This also creates issues
if you use anything that parses your css such as grunt-cache-bust.

This adds a noop rule at the end of each keyframes definition, leading
to valid css

@arbylee
Copy link
Author

arbylee commented Dec 19, 2014

This should fix issues seen in #139 and #129. Not my favorite code, but I'm hoping to get a discussion going about other possible solutions. From what I could tell, lessc is the one adding that additional semicolon, which is actually invalid for a keyframes definition

Context: Lessc is adding a semicolon at the end of keyframes definition, which is
invalid css and causes issues on some devices.  This also creates issues
if you use anything that parses your css.

This adds a noop rule at the end of each keyframes definition, leading
to valid css
@OpakAlex
Copy link

OpakAlex commented Apr 2, 2015

@arbylee problem with @-webkit-keyframes too. you fix in @Keyframes... but not in @-webkit-keyframes

@rlecaro2
Copy link

I'm currently using your fix so my grunt compiles correctly. I suscribed to this thread so I can port my lesshat version when this is merged.

Thanks, @arbylee.

@ndesorden
Copy link

Thanks arbylee, your fix works perfectly.

The extra colon a the top of a css file was causing htc one "not understand" some following css rules!

@Remco75
Copy link

Remco75 commented Oct 22, 2015

nice one, will it be merged, or will there be another fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants