W3C home > Mailing lists > Public > public-svg-wg@w3.org > April to June 2010

Re: paths-data-20-f.svg

From: Alex Danilo <alex@abbra.com>
Date: Fri, 21 May 2010 13:22:03 +1000
Message-Id: <RO2R2L.4VE4HHE6L9DI@abbra.com>
To: Alex Danilo <alex@abbra.com>
Cc: public-svg-wg@w3.org
Answering myself:

You wrote:
>Hi All,
>	I've been looking at paths-data-20-f.svg which is supposed to
>test 1.1F2 Errata.
>	I don't see any errata relating to this test, but more
>importantly it appears to be inconsistent with the current draft.
>	For example, one of the sub-tests (I haven't looked at
>all of them yet) contains:
>    <!-- out of range large-arc-flag value -->
>    <path d="M280,120 h25 a25,25 0 1,0 -25,25 z" fill="lime" stroke="lime"/>
>    <path d="M280,120 h25 a25,25 0 6 0 -25,25 z" fill="red"/>
>	In the test matrix, Opera and Firefox have passes against them
>while everyone else fails.
>	It appears that the test is expecting rejection of the path with
>the 'out of range' large arc flag.
>	However, the original 1.1 spec and the current 1.1F2 draft
>both state in the Elliptic Arc implementation notes:
>"Any nonzero value for either of the flags fA or fS is taken to mean the value 1."
>	So either the test is wrong, or the spec. has not been corrected
>to indicate this is meant to be an error condition.

The BNF in the main part of the spec mandates the '0' or '1' for the

So, the Elliptic Arc implementation notes need to be corrected.


Received on Friday, 21 May 2010 03:22:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:29:43 UTC