- From: Matt Perry via GitHub <sysbot+gh@w3.org>
- Date: Fri, 17 Jan 2020 12:50:54 +0000
- To: public-houdini-archive@w3.org
@majido > First it is not clear to me why a stateless animator needs to receive "options" given that its output should only be dependent on its animate() input currentTime. There's a difference between configurable animations and stateful animations. We set options for every keyframes animation but I wouldn't consider them stateful when they can be resolved for `t`. Likewise there are spring physics implementations that resolve for t (stateless) and those that integrate time into the previous state (stateful). For instance, we might want to create a new tween/keyframes animation implementation that accepts references to easing functions not already available in the WebAnimations API that can't be described with a bezier curve (https://github.com/Popmotion/popmotion/blob/master/packages/easing/src/index.ts#L49) Options and state are different for this reason. -- GitHub Notification of comment by InventingWithMonster Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/869#issuecomment-575613370 using your GitHub account
Received on Friday, 17 January 2020 12:50:56 UTC