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

Platform evolution and attributeType="auto"

From: Robert O'Callahan <robert@ocallahan.org>
Date: Tue, 11 Aug 2009 11:58:35 +1200
Message-ID: <11e306600908101658q2f1a7efaubcc88a6f04362e32@mail.gmail.com>
To: www-svg <www-svg@w3.org>

It seems to me that attributeType="auto" (the default!) makes it difficult
to evolve the platform. In particular, if the SVG WG (or some other group)
decides to make more CSS properties animatable via SVG, and those properties
happen to have the same names as existing (or future) animatable SVG
attributes, the behaviour of existing content using attributeType="auto"
might change.

Now, it might be that this wouldn't be a problem in practice, since the
existing animatable attribute would quite likely be defined to map directly
in the new CSS property, so animating it as a CSS property would give the
same results as animating the attribute. But it does mean that you're going
to have to think very carefully before adding more CSS properties animatable
with SVG.

"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
Received on Monday, 10 August 2009 23:59:15 UTC

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