- From: Boris Chiou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Mar 2023 00:13:19 +0000
- To: public-fxtf-archive@w3.org
> The way it's defined, it'll also result in funky animation behavior for animating from 0% to 100% - depending on the angle, it'll reach its "max distance" at varying %s, so a bunch of elements all animating from the center to the edge at once will "hit the edge" at different points in their animations. Similarly, an animation from the edge to the center will look like it's delayed for an unpredictable amount of time (while it's still past its "max distance"), and then depending on angle will start moving at different times. Agree. The animation may look weird because the used offset-distance is different from the expected one. I have no specific thought for this. This simplification looks good for animations (and I believe the most of the use cases of motion path is for animations), so I'm happy with it. Besides, the original math calculation is really complicated, as you mentioned, and it's also great to simplify the position calculation. No objection for this proposal. -- GitHub Notification of comment by BorisChiou Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/363#issuecomment-1449119376 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 1 March 2023 00:13:21 UTC