Re: [css-houdini-drafts] Allow animators to specify their desired frame rate

Here is the relevant discussion from IRC log:

**dino**: Also would like a flag specifying how fast timeline should pump. rAF is kinda 60Hz, but we now have variable-rate screens coming out, etc. 
**dino**: So question is how to specify that from a worklet - message to the timeline saying "i wanna get called back more frequently/in at least 4ms"? And some feedback saying you're not meeting that goal, so you're getting scaled back. 
**flackr**: Would you ever not want to run that fast? 
**dino**: Yes, if your animation doesn't need to be 120hz, it's better to run at 60hz for power reasons. 
**astearns** appreciates the verb tenses I might have used in those imaginable states where I would have been smart enough to talk about speculative threads 
**TabAtkins**: This kinda sounds like various stream APIs, which let you attach to timelines at various coarseness. 
**brucel** +1 to what tab said "if your animation doesn't need to be 120hz, it's better to run at 60hz for power reasons." - Opera desktop, for example, has power saving mode in which frame rate for video and animations is deliberately reduced 
**dino**: and figuring out how fast a timeline *can* be pumped, asking for a particular pump rate, and getting updates that you're missing the deadlines and will be slowed from your requested rate. 
**dino**: We tried running rAF at 120hz, but some animations *assume* it runs at 60hz and don't actually check the time delta, so they just run double-speed and break. 
**dino**: We also determined that 120hz animations do use a ton more power. 
**astearns** brucel that was actually dino 
**brucel** This baffling new "IRC" technology is hard, apologies dino
**dino**: And there's some intermediate stuff - if you run at 120hz, but determine there was no change, don't repaint the screen. 
**flackr**: Maybe speculate that it doesn't change, and throttle down?
**dino**: We see today's code, where people just run a rAF at all times...
**Rossen**: Speculating throttling based on update is tricky - position sticky needs fast updates, but does nothing until the element sticks...

-- 
GitHub Notification of comment by majido
Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/813#issuecomment-417053951 using your GitHub account

Received on Wednesday, 29 August 2018 18:19:44 UTC