We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Haven't checked this deeply but on first look it seems that the prefixing breaks keyframe definitions, for example, for a prefix _R,
_R
@keyframes mdl-spinner__layer-4-fade-in-out { from { opacity: 0; } 65% { opacity: 0; } 75% { opacity: 0.99; } 90% { opacity: 0.99; } 100% { opacity: 0; } }
@-webkit-keyframes mdl-spinner__layer-4-fade-in-out { ._R 0%, ._R 65%{ opacity:0 } ._R 75%, ._R 90% { opacity:.99 } ._R to{ opacity:0 } }
which breaks the keyframe definition.
Basically prefixing shouldn't be applied at all on keyframe definitions? (since the actual rule that uses them will be prefixed anyways)
The text was updated successfully, but these errors were encountered:
Thanks for reporting! I'll examine this by this weekend and report back.
Sorry, something went wrong.
fixed in version 0.1.7 on npm @inakianduaga, please update the package and check it out thanks!
@pazams Works like a charm, thanks!
Successfully merging a pull request may close this issue.
Haven't checked this deeply but on first look it seems that the prefixing breaks keyframe definitions, for example, for a prefix
_R
,which breaks the keyframe definition.
Basically prefixing shouldn't be applied at all on keyframe definitions? (since the actual rule that uses them will be prefixed anyways)
The text was updated successfully, but these errors were encountered: