W3C home > Mailing lists > Public > public-fxtf-archive@w3.org > August 2017

[fxtf-drafts] [motion-1] Direction of offset-rotate at segment boundaries

From: Kari Pihkala via GitHub <sysbot+gh@w3.org>
Date: Mon, 07 Aug 2017 06:17:10 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issues.opened-248316704-1502086628-sysbot+gh@w3.org>
karip has just created a new issue for https://github.com/w3c/fxtf-drafts:

== [motion-1] Direction of offset-rotate at segment boundaries ==
The direction at segment boundaries used by [offset-rotate](https://drafts.fxtf.org/motion-1/#offset-rotate-property) came up during discussion about the SVG [`pathAngleAtLength()`](https://github.com/w3c/svgwg/issues/338) function. I’m opening this issue to get more feedback.

The direction at segment boundaries can be either the direction of the previous path segment or the direction of the next path segment.

Animation software seems to use either of them. After Effects seems to use the direction of the previous path segment. Apple Motion seems to use the direction of the next path segment.

CSS Motion Path defines the direction to be the direction of the previous path segment and Google Chrome has implemented it that way.

Should it be changed to be the direction of the next path segment?

[SVG 2 Path Directionality](https://svgwg.org/svg2-draft/paths.html#PathDirectionality) defines __the direction at the start of a path segment__ and __the direction at the end of a path segment__. CSS Motion Path could be changed to reference either of them to get a more precise definition which covers also zero-length subpaths.


Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/209 using your GitHub account
Received on Monday, 7 August 2017 06:17:14 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 November 2018 00:45:59 UTC