Ehsan Karamad

The initial motivation as I understand is blocking animations from using up CPU cycles (for main frame responsiveness). As for an application right now I can think of ``s and...

To conclude this thread so far: - To have a feature to *limit* use of declarative animations is useful because 1. It reduces CPU usage and makes the page more...

Thanks for filing these. I will get back to this thread and fix the explainer after concluding the main promise of the feature mostly discussed in issues w3c/document-policy#10 and w3c/webappsec-permissions-policy#204.

Reviving this thread as the animation policy has been reworked. It no longer deals with *composited* animations and is now about disabling certain *layout* animations instead. Please, take another look.

(apologies for the delayed response) Thanks for the comment's and corrections. I created the pull request w3c/webappsec-permissions-policy#239 to address the mentioned issues. AFAIK on Chrome the aforementioned animations do not...

Thanks for the issue. A blocked animation is expected to still run but at a very reduced sampling/interpolation rate. From the explainer > ... These properties are "animated" by simply...