W3C home > Mailing lists > Public > www-svg@w3.org > October 2010

RE: <animateColor>

From: Anthony Grasso <Anthony.Grasso@cisra.canon.com.au>
Date: Tue, 12 Oct 2010 23:43:54 +0000
To: ddailey <ddailey@zoominternet.net>
CC: "www-svg@w3.org" <www-svg@w3.org>, Alex Danilo <alex@abbra.com>, Chris Lilley <chris@w3.org>
Message-ID: <923A4276C1903646BE5299CA8462B0A0059FFA@EXM02-WVP.cisra.canon.com.au>
Hi David,

> -----Original Message-----
> From: www-svg-request@w3.org [mailto:www-svg-request@w3.org] On Behalf
> Of Chris Lilley
> Sent: Wednesday, 13 October 2010 8:27 AM
> To: ddailey
> Cc: www-svg@w3.org
> Subject: Re: <animateColor>
> On Tuesday, October 12, 2010, 2:26:51 PM, ddailey wrote:
> d> What does <animateColor> give us that <animate> doesn't?
> At this point, it gives nothing besides compatibility with content that
> uses it.

As far as I can tell, the 'color-interpolation' property applies to <animateColor> but does not indicate that it applies to <animate>. Note: this is highlighted in Mozilla bug tracker pointed out in Roberts email. Hence, more appealing colour transitions could be achieved using <animateColor> and setting 'color-interpolation' property to linearRGB.

Not sure if there is a way to set the color interpolation on <animate>. Unless there is something I've missed. Alex, Chris?


> Originally, SVG just had animateColor (from SMIL) and animate (from
> SMIL, which could animate unitless scalar values, or space separated
> lists of unitless scalar values.
> The smil folks were mainly looking at the lexical representation, so
> even #3F7 seemed like a non scalar value and certainly mediumPapayaWhip
> looked nothing like a scalar.
> SVG, partly as a result of comments, extended animate to allow
> animation of attributes and properties which are, in fact once you
> understand them, lists of scalars. In other words, a benefit of
> integrating SMIL deeper into the host language of SVG was that it 'knew
> about' some attributes.
> So #56F7C9 and rgb(12, 57, 98) and mediumPapayaWhip and currentColor
> and inherit are different lexical forms which at the end of the day
> evaluate to a triple of red, green and blue unitless scalar values,
> which SMIL-in-SVG can then happily animate.
> That was rather later in the development of SVG though, and by then we
> already had animateColor so it was not removed.
> d> I can't tell if the spec requires it,
> It does, although this was a later development in SVG and we kept
> around animateColor as well. Its also clearer in 1.1 than 1.0, clearer
> in 1.2T than 1.1, and clearer again in 1.1SE.
> d> but all browsers seem to allow <animate
> d> attributeName="fill" values="purple;plum;papayawhip"  ...etc...>
> just fine.
> d> Is it just out of the kind hearts of the browsers that this works or
> does
> d> the spec require it?
> The latter, plus the desire to not needlessly break content that uses
> it.
> --
>  Chris Lilley   Technical Director, Interaction Domain
>  W3C Graphics Activity Lead, Fonts Activity Lead
>  Co-Chair, W3C Hypertext CG
>  Member, CSS, WebFonts, SVG Working Groups

The information contained in this email message and any attachments may be confidential and may also be the subject to legal professional privilege. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorised and prohibited. If you have received this email in error, please immediately advise the sender by return email and delete the information from your system.
Received on Tuesday, 12 October 2010 23:44:31 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:23 UTC