- From: Majid Valipour via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Aug 2018 18:19:32 +0000
- To: public-houdini-archive@w3.org
_From @flackr on February 13, 2018 16:54_ I like having an explicit state object. If the developer stores nothing in that state then we assume that since it is okay to shut down and resume their animation with no state that it should also be okay to speculatively execute on future values (until doing so results in state being used at which point we have to stop, destroy the speculative animation, and restart it at the point before it became stateful). The nice thing about this is that the developer doesn't have to think about whether their animation is stateful upfront, and could even have animations that transition between being stateful and stateless based on inputs (e.g. stateful while an object has momentum, stateless when it comes to rest). -- GitHub Notification of comment by majido Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/812#issuecomment-417053894 using your GitHub account
Received on Wednesday, 29 August 2018 18:19:36 UTC