W3C home > Mailing lists > Public > public-svg-wg@w3.org > July to September 2011

Re: rotated path segment proposal

From: Leonard Rosenthol <lrosenth@adobe.com>
Date: Mon, 25 Jul 2011 11:12:23 -0700
To: Dirk Schulze <dirk@dschulze.com>
CC: Cameron McCormack <cam@mcc.id.au>, SVG WG <public-svg-wg@w3.org>
Message-ID: <CA5329E3.6DD1%lrosenth@adobe.com>
We are talking about changing the syntax of the path element, yes?  If so,
that means that if an SVG file using these new possible operators in the
value is read by an old/existing reader, the behavior is completely
undefined!  What is it going to do with it?!?!?

Separate segment
	<path d="....">
	<path d="...">
Instead of
	<path d="... R ....">


On 7/25/11 1:06 PM, "Dirk Schulze" <dirk@dschulze.com> wrote:

>Am 25.07.2011 um 18:46 schrieb Leonard Rosenthol:
>> Wouldn't it be easier to just have two separate segments, and then just
>> change the rotation on the second??   Why would you need a single
>What do you mean with two separate segments?
>> I simply don't see enough of a use case for this to SIGNIFICANTLY break
>> backwards compatibility by adding new operators to the path segment
>> format.  Do we even have any idea what such an addition to do to
>> solutions when they encountered this??
>I don't see how this breaks backward compatibility. If someone used f, r
>or even ~ before, the path gets suddenly valid but definitely was invalid
Received on Monday, 25 July 2011 18:13:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:20:13 UTC