W3C home > Mailing lists > Public > public-fx@w3.org > April to June 2015

Re: [motion] direction and starting point of circle/ellipse

From: Dirk Schulze <dschulze@adobe.com>
Date: Fri, 17 Apr 2015 11:14:08 +0000
To: Tab Atkins Jr. <jackalmage@gmail.com>
CC: Erik Dahlström <ed@opera.com>, "public-fx@w3.org" <public-fx@w3.org>, "www-svg@w3.org" <www-svg@w3.org>
Message-ID: <964B3A28-1CC0-4CD3-BDDE-21C8165D3E25@adobe.com>

> On Apr 16, 2015, at 10:42 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> 
> 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.

Since 3 o’clock is implemented for stroke dash arrays already. I agree that motion path should change as well.

Greetings,
Dirk

> 
> ~TJ
> 

Received on Friday, 17 April 2015 11:14:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:49:54 UTC