You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The bug appears to have been introduced around this commit: e85da87
Using the mousewheel messes with the frame timing for a second or so after each mousehweel event.
With each refresh the severity of the bad frame timing can vary.
In Chrome's perfomance profiler it shows a load of 'partially presented frames' when this occurs, I've uploaded a copy of the profiler dump:
The bug appears to have been introduced around this commit:
e85da87
Using the mousewheel messes with the frame timing for a second or so after each mousehweel event.
With each refresh the severity of the bad frame timing can vary.
In Chrome's perfomance profiler it shows a load of 'partially presented frames' when this occurs, I've uploaded a copy of the profiler dump:
Trace-20260629T122706.json.gz
Video:
Test.-.Google.Chrome.2026-06-29.12-32-56.mp4
Just observe the frame time graph in the video to see a demonstration of what's happening.
As far as I can tell it's only the mousewheel that has this effect. Other input events are fine.
And it appears to only affect the HTML5 target.