Open mathiasbynens opened 10 years ago
@Yeswanth-JG Thanks for taking a look! Which version of Opera did you try this in exactly? Are you on Win/Mac?
If prefix-free is intended for the stable releases, then no matter about the issue on prefixing beta channels.!
No disagreement here :) Consider this a ‘heads up’ kind of ticket — something to keep an eye on.
@mathiasbynens @LeaVerou After enabling below flag
chrome://flags/#enable-experimental-web-platform-features
chrome is going into non-stable (beta) experimental zone. But, there also, -webkit-
prefix is working for the animation
property.
@mathiasbynens
-webkit-
manuallyanimation
property works.I think it should be fixed with prefix-free.
@Yeswanth-JG I know, that’s what the issue I filed here is about: https://code.google.com/p/chromium/issues/detail?id=341003
It’s not a bug in prefix-free (although prefix-free could work around it if you wanted to).
I believe I'm seeing this now in stable (Version 34.0.1847.116). Seeing the reduced test case above produces the error state (no animation), though curiously, disabling and re-enabling the animation via dev tools makes the animation begin. Am I the only one seeing this?
Reduced test case: http://mathiasbynens.be/demo/prefixfree-chromium
In Opera 20+ (Next) and Chrome 33+ (Beta/Canary), the
#animate
element getsanimation: move 3s ease infinite
applied to it (as in the source CSS). Because of this, no animation is visible.In Chrome 32 or Opera 19,
-webkit-animation
is used instead, and the animation is displayed correctly.