- From: Majid Valipour via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Aug 2018 18:19:32 +0000
- To: public-houdini-archive@w3.org
@asajeffrey we have been thinking about similar mechanism for stateful animator but with a callback instead. Rather than a explicit object that may be deep cloned at "any point" we have been favoring a `onDestroy` callback that returns a object which is then deep cloned. Here is the [basic](https://wicg.github.io/animation-worklet/#migrating-animator) idea. One advantage of callback is that the animator does not have to maintain the state object all the time but only when we are migrating between contexts. I expect migrations to be infrequent in which case this can lead to a more optimal outcome. I suppose if we have an state object then its existence can also play the role of `hasState` as well. Slightly better API but has its own set of complications. BTW, it was implied in original comment but I want to make it explicit that I think it is best to treat `hasState` as static property of animator that is considered constant during its lifetime while the actual `state` is dynamic. -- GitHub Notification of comment by majido Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/812#issuecomment-417053887 using your GitHub account
Received on Wednesday, 29 August 2018 18:19:36 UTC