- From: Kari Pihkala via GitHub <sysbot+gh@w3.org>
- Date: Mon, 31 Jul 2017 10:12:26 +0000
- To: public-svg-issues@w3.org
Oops, again! Animation software isn’t as consistent as I thought. I just checked how [Apple Motion](https://www.apple.com/final-cut-pro/motion/) works, and it uses the direction of the next segment at vertices (and behaves strangely at the end). Here’s a screen capture of it:  I don’t have access to After Effects right now, but it worked the same way as CSS Motion Path when I tried it. Unfortunately, [After Effects help documentation about motion paths](https://helpx.adobe.com/after-effects/using/assorted-animation-tools.html) doesn’t go into details like that. It would be nice to know why the Chromium team decided to implement motion paths the way they did. When I [requested the addition](https://github.com/w3c/fxtf-drafts/issues/108) to CSS Motion Path, I just wanted Chrome’s behavior to be documented somehow. -- GitHub Notification of comment by karip Please view or discuss this issue at https://github.com/w3c/svgwg/issues/338#issuecomment-319026463 using your GitHub account
Received on Monday, 31 July 2017 10:12:28 UTC