Re: requestAnimationFrame rate for background tabs and offscreen instances

"L. David Baron" <[email protected]> Tue, 1 Sep 2015 18:04:00 -0700

Newsgroups	gmane.comp.mozilla.devel.layout
Message-ID	<[email protected]>

On Wednesday 2015-09-02 10:53 +1000, Cameron McCormack wrote:
> Boris Zbarsky:
> > The real question here is what should get throttled.  Just rAF?  Or
> > everything we run off the refresh driver (rAF, SMIL animations, CSS
> > transitions/animations, etc)?  The latter fire page-visible events
> > that might well break pages if we turn them off completely, but I'm
> > probably OK throttling them all off altogether as long as Chrome
> > does the same thing (and we're sure they're doing it; e.g. they ship
> > it).
> 
> This is the kind of thing the Google folks want to standardise in their
> “rendering pipeline” spec.  From what I understood, they want to
> throttle everything.  I have no idea if that is what they currently do.

Yes, http://logs.csswg.org/irc.w3.org/houdini/2015-08-29/#e589936
was very clear that they would want to throttle everything together;
I think I was under the impression that they currently only throttle
rAF.

But one of the key concepts they want to standardize in the
rendering pipeline spec is that there's a set of stuff that needs to
all happen together and cannot happen separately.

-David

-- 
𝄞   L. David Baron                         http://dbaron.org/   𝄂
𝄢   Mozilla                          https://www.mozilla.org/   𝄂
             Before I built a wall I'd ask to know
             What I was walling in or walling out,
             And to whom I was like to give offense.
               - Robert Frost, Mending Wall (1914)

_______________________________________________
dev-tech-layout mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-layout

signature.asc (application/pgp-signature, 819 B)