28876 2015-07-01 22:25:42 +0000 Doing too much stuff around animation frame tick may cause rendering updates to be postponed 2019-03-29 19:16:00 +0000 1 1 1 Unclassified WHATWG HTML unspecified PC All RESOLVED NEEDSINFO P2 normal Unsorted 28001 1 bugs ian annevk d dbaron mike zcorpan contributor oldest_to_newest 121564 0 bugs 2015-07-01 22:25:42 +0000 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. 123493 1 annevk 2015-10-06 07:02:22 +0000 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. 123525 2 bugs 2015-10-06 16:48:47 +0000 https://bugzilla.mozilla.org/show_bug.cgi?id=1149555 129648 3 d 2019-03-29 19:16:00 +0000 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.