- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Aug 2019 18:42:02 +0000
- To: public-houdini-archive@w3.org
flackr has just created a new issue for https://github.com/w3c/css-houdini-drafts: == [css-animationworklet] Stateful animator section should focus on developer visible details == The [Stateful animator](https://drafts.css-houdini.org/css-animationworklet/#stateful-animator-desc) section could be much more succinct by explaining the developer-visible guarantees. i.e. A stateful animator is guaranteed to run on a unique animator instance. For the lifetime of the WorkletAnimation, if the Animator Instance is destructed before the WorkletAnimation, the user agent will invoke the animator definition's state function and associate the result with the WorkletAnimation. When an Animator Instance is recreated for a WorkletAnimation, this associated state is passed in to the constructor. This is described in detail in <other sections which describe state serialization>. Then, we could have the note and explain how this means your animation's state will persist throughout the animation as long as you provide it in the state function and restore it in the constructor. Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/930 using your GitHub account
Received on Thursday, 15 August 2019 18:42:04 UTC