New issue
Advanced search Search tips

Issue 824026 link

Starred by 5 users

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Drive AnimationContainer from compositor instead of base::RepeatingTimer

Project Member Reported by alancutter@chromium.org, Mar 21 2018

Issue description

gfx::AnimationContainer uses base::RepeatingTimer to drive animations instead of listening for compositor driven frame requests.

Being driven by the compositor would enable UI animation frames to be based on scheduler logic that takes into account monitor refresh rates and heavy CPU loads.
It would also make testing of UI animations much cleaner as you could jump forwards by arbitrary amounts of time without processing every single 60Hz frame inbetween.
 
Labels: Hotlist-GoodFirstBug
Status: Available (was: Untriaged)
Is this good first bug material? If not, feel free to remove the label.
I get what the base::RepeatingTimer does. It triggers a callback every time interval as far as i understand. I wanted to give it a try. In this issue , AnimationContainer should implement CompositorAnimationObserver .. Just trying to understand the code. I apologies if my questions are silly.
#2: Questions are good, communication is good.
Labels: Hotlist-DesktopUIChecked Hotlist-DesktopUIToolingRequired

Sign in to add a comment