W3C home > Mailing lists > Public > www-svg@w3.org > July 2009

Re: Error report for SVG 1.1 Appendix N, regarding "Animatable" field for 'baseline-shift', 'font-size-adjust', and 'stroke-dasharray'

From: Cameron McCormack <cam@mcc.id.au>
Date: Thu, 23 Jul 2009 11:37:08 +1000
To: Daniel Holbert <dholbert@mozilla.com>
Cc: www-svg@w3.org
Message-ID: <20090723013708.GA30471@arc.mcc.id.au>
Hi Daniel.

Daniel Holbert:
> I'm writing to report an inconsistency in the SVG 1.1 spec.  In
> "Appendix N: Property Index", the "Animatable" fields for the
> 'baseline-shift' and 'font-size-adjust' properties are different from
> what their explicit property definitions say.  Additionally,
> 'stroke-dasharray' is completely missing its entry for "Animatable" in
> Appendix N's table.

Thanks for the bug report.  These are fixed in the current SVG 1.1
Second Edition editor’s draft:

  http://dev.w3.org/SVG/profiles/1.1F2/publish/propidx.html

although it has been fixed to just say “yes” or “no”, and not to
duplicate the restrictions listed in the main chapters.

> I think it's sensible for baseline-shift to be additive
> (at least when its value is a <length>),

Agreed.

> whereas it's not sensible for font-size-adjust to be additive.

It’s probably not useful, agreed.

> As a side note, I'm not entirely sure why some properties say
> "(non-additive, 'set' and 'animate' elements only)", when
> "stroke-dasharray" only says "(non-additive)".  Is the "'set' and
> 'animate' elements only" prose  merely stating that you can't animate
> the particular property using 'animateColor' and 'animateTransform'
> elements?  Surely that is true of most properties, though it's only
> explicitly specified on very few...  Anyway, though, that's a separate
> and less important issue.

Yeah I think the “'set' and 'animate' elements only” text is just a
distraction.

> Here are my proposed changes -- basically just making Appendix N match
> the longer property definitions for these three properties.

Thanks.  I might add notes back to the table to indicate which support
only additive animation.


A separate issue is that the concept of “additive animation” here, in
respect to the property/attribute definitions, is a bit blurry.  I take
it to mean “supports numerical interpolation, as well as additive and
cumulative animations”.  I don’t think that’s stated anywhere in the
spec.  That might have been an issue we pushed off until SVG 2.0.

-- 
Cameron McCormack ≝ http://mcc.id.au/
Received on Thursday, 23 July 2009 01:37:59 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:42 GMT