- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 06 Mar 2023 19:08:54 +0000
- To: public-fxtf-archive@w3.org
tabatkins has just created a new issue for https://github.com/w3c/fxtf-drafts: == [motion-1] "equivalent path" mismatch for circles between SVG and Motion == Both SVG and Motion define equivalent paths for an essentially identical set of shapes. For rectangles and polygons, their definitions are identical, but for circles/ellipses they're not - SVG defines that a circle's equivalent path starts at its rightmost point (cx + rx, cy), while Motion defines that it starts at its topmost point (cx, cy - ry). They at least both agree that the path continues clockwise. Should we align these definitions? I'm inclined to take SVG's definition just because it has earlier claim, and it seems more likely to break something if we changed SVG. Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/506 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 6 March 2023 19:08:56 UTC