On Sunday, March 22, 2015 at 3:28:13 AM UTC+9, Patrick Walton wrote: > One remaining issue is how to deal with jQuery-style animations that are > done with setTimeout(). They have to contend with everything else on the > DOM/script thread to avoid breaking the HTML/JavaScript event loop > semantics. I've brainstormed ideas for doing some sort of fair scheduling > for events on the main thread to try to give animations priority wherever > possible, but anything like this still has to deal with the > run-to-completion for event handlers that hog the CPU. I'm open to ideas > here.
Implementing element.animate() would give authors a means of creating animations from script that run on the compositor (but that's not going to help with existing content). I wonder if you considered implementing Web Animations first and building CSS Animations/Transitions on top of it? That would probably be easier than trying to retrofit the API later (which is what we're currently doing in Gecko). Best regards, Brian _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
