- From: Jatinder Mann <jmann@microsoft.com>
- Date: Thu, 11 Oct 2012 20:30:28 +0000
- To: James Robinson <jamesr@google.com>, Boris Zbarsky <bzbarsky@mit.edu>
- CC: "public-web-perf@w3.org" <public-web-perf@w3.org>
On Thu, Oct 11, 2012 at 1:11 PM, James Robinson wrote: >>On Thu, Oct 11, 2012 at 12:51 PM, Boris Zbarsky wrote: >> Now maybe declarative animation events should _also_ not fire in background tabs. >> I would be a lot happier with that than in having requestAnimationFrame get out of sync >> with declarative animations. >> > That would be best! We should bring this up with with the WGs that are responsible for > animation events, CSS mainly, and see what they think. We've had compat issues when > we've accidentally stopped firing such events in background tabs but haven't made a > serious effort to work through them with the standards bodies and see if we could find > a solid solution. I agree that the most CPU efficient thing would be to not animate something that the user cannot visibly see. Working with the appropriate WG is the right thing to do. Jatinder
Received on Thursday, 11 October 2012 20:34:11 UTC