- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 16 Apr 2015 13:42:38 -0700
- To: Erik Dahlström <ed@opera.com>
- Cc: "public-fx@w3.org" <public-fx@w3.org>, "www-svg@w3.org" <www-svg@w3.org>
On Thu, Apr 16, 2015 at 12:33 AM, Erik Dahlström <ed@opera.com> wrote: > Hi, > > forwarding on behalf of Eric Willigers, who found some inconsistencies in > how the starting point and direction works in the motion path draft compared > to svg2. In the definition of the motion-path[1] property the starting point > and direction for circle and ellipse are different to the ones used for the > equivalent paths in svg2, see [2][3]. In svg the equivalent path for circle > and ellipse starts at 3 o'clock and proceeds clockwise. > > Is this going to be a possible cause of confusion, and should these > definitions be aligned? > > > [1] http://dev.w3.org/fxtf/motion-1/#motion-path-property > [2] https://svgwg.org/svg2-draft/shapes.html#CircleElement > [3] https://svgwg.org/svg2-draft/shapes.html#EllipseElement Yeah, given Tav's work that established the starting point for shapes is remarkably consistent across browsers, Motion Path should change to start circle()/ellipse() at the 3 o'clock point. ~TJ
Received on Thursday, 16 April 2015 20:43:25 UTC