On Thu, Nov 6, 2014 at 1:56 PM, L. David Baron <[email protected]> wrote:
> But each tick of the animated image (which I believe is a background > image) sends us through ImageLoader::DoRedraw, which in turn calls > nsIFrame::SchedulePaint, so that we do display list analysis to see > if anything changed. (Nothing has, since the image is well > offscreen.) But constructing and comparing the display lists takes > a good bit of time, leading to twitter using a good bit of CPU when > it's being displayed. > > Is it reasonable to test that the image is offscreen (or, really, > not in the region that's painted into a layer) somewhere earlier in > the process here? Or is there something else we should be doing to > avoid this? > Definitely. I think we can avoid the SchedulePaint if InvalidateImagesCallback doesn't find anything to invalidate. Got a bug number? Rob -- oIo otoeololo oyooouo otohoaoto oaonoyooonoeo owohooo oioso oaonogoroyo owoiotoho oao oboroootohoeoro oooro osoiosotoeoro owoiololo oboeo osouobojoeocoto otooo ojouodogomoeonoto.o oAogoaoiono,o oaonoyooonoeo owohooo osoaoyoso otooo oao oboroootohoeoro oooro osoiosotoeoro,o o‘oRoaocoao,o’o oioso oaonosowoeoroaoboloeo otooo otohoeo ocooouoroto.o oAonodo oaonoyooonoeo owohooo osoaoyoso,o o‘oYooouo ofooooolo!o’o owoiololo oboeo oiono odoaonogoeoro ooofo otohoeo ofoioroeo ooofo ohoeololo. _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
