W3C home > Mailing lists > Public > public-fx@w3.org > January to March 2011

Re: Some practical issues integrating the SVG transform attribute with CSS transform properties

From: Robert O'Callahan <robert@ocallahan.org>
Date: Sun, 27 Mar 2011 09:00:07 +1300
Message-ID: <AANLkTinPyZRJc4dtdqo8vq-21Tq9zacVvYfLnLjDX2y1@mail.gmail.com>
To: "Dr. Olaf Hoffmann" <Dr.O.Hoffmann@gmx.de>
Cc: public-fx@w3.org
2011/3/27 Dr. Olaf Hoffmann <Dr.O.Hoffmann@gmx.de>

> But similar things apply for some features of the current CSS2.1 draft
> compared to CSS2.0 (used by SVG 1.1) - and of course there are even more
> version-dependent features in HTML ;o)
>

CSS and HTML do not respect version switches. I.e. there is no way for a
document to say "I am CSS 2.0 and HTML3" and get the behavior specified by
CSS 2.0 and HTML3 instead of whatever the latest specs say. When CSS or HTML
specs change, we change the behavior for *all* documents.

(There is a "quirks mode" switch but it doesn't map onto spec versions and
we are not adding to it.)

SVG transformations are often used in current SVG documents, therefore
> either
>
future recommendations are compatible with current SVG recommendations,
> or version-dependent and profile-dependent viewer behaviour is necessary
> for a huge amount of documents.
>

Future recommendations need to be compatible with current recommendations,
or at least we need to be confident that any changes will break only an
insignificant amount of Web content. This is the way the rest of the Web
works, and SVG should be consistent with that.

Rob
-- 
"Now the Bereans were of more noble character than the Thessalonians, for
they received the message with great eagerness and examined the Scriptures
every day to see if what Paul said was true." [Acts 17:11]
Received on Saturday, 26 March 2011 20:00:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 26 March 2011 20:00:43 GMT