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
[Feature policy: animations] What does "blocking" an animation mean? #12
Comments
Thanks for the issue. A blocked animation is expected to still run but at a very reduced sampling/interpolation rate. From the explainer
so potentially the behavior could be an abrupt transition to the final state (perhaps in the middle or at the end of the interval).
Yes, they should; and the behind-the-flag implementation on Chrome seems to support that as expected. In tested this on a demo page here by listening to the
Good point...maybe just disallow the whole animation (in favor of a more consistent and potentially simpler implementation). |
That sentence is in the context of describing how properties with an animation type of "discrete" currently animate. It doesn't define how "blocked" animations are expected to work with this policy. |
Revised the animations policy to propose a modified policy that blocks layout inducing animations as opposed to the non-composited animations. The changed is motivated discussions in issues #202, #203, and #204.
Revised the animations policy to propose a modified policy that blocks layout inducing animations as opposed to the non-composited animations. The changed is motivated discussions in issues #202, #203, and #204.
Element.animate()
with a disallowed property throw?The text was updated successfully, but these errors were encountered: