This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28876 - Doing too much stuff around animation frame tick may cause rendering updates to be postponed
Summary: Doing too much stuff around animation frame tick may cause rendering updates ...
Status: RESOLVED NEEDSINFO
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 28001
  Show dependency tree / graph
 
Reported: 2015-07-01 22:25 UTC by Olli Pettay
Modified: 2019-03-29 19:16 UTC (History)
5 users (show)

See Also:
annevk: needinfo? (dbaron)

Attachments

Description Olli Pettay 2015-07-01 22:25:42 UTC 
I made Gecko to follow the resize event handling from the spec, but got backed out because of performance regressions. Firing different events and calling callbacks right before the rendering update may force browser to postpone the update a bit. Just too much stuff happening around the animation frame tick time.

I don't have a proposal how this all should work, but somehow we should try
to spread the work more evenly over the animation frame interval.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28644 is also related.
Comment 1 Anne 2015-10-06 07:02:22 UTC 
Olli, do you have a pointer to the Gecko bug where you attempted this?

David, I remember you having concerns about the current setup as well. Any ideas for what we should do instead?

I don't really want to double down on this approach, but not defining this doesn't let us define some other things in detail, e.g., how Fullscreen works.
Comment 3 Domenic Denicola 2019-03-29 19:16:00 UTC 
Not sure what to do here with this bug, and Bugzilla is closing down, so I will close it. Feel free to open a new issue on https://github.com/whatwg/html/issues so we can have further discussion.