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

Re: Why are <svg> elements not SVGTransformable?

From: Jeff Schiller <codedread@gmail.com>
Date: Sun, 21 Feb 2010 08:28:49 -0600
Message-ID: <da131fde1002210628m4191e335s78ba67a3ba9779c2@mail.gmail.com>
To: Robert Longson <longsonr@gmail.com>
Cc: www-svg@w3.org
No, it's not really a hardship :)

It just seems that, if the <svg>'s x,y values are ignored when it's at
the top-level, the @transform could also similarly be ignored.

It just seemed like an arbitrary choice that I was curious about - the
<svg> element is the only SVG element that doesn't have a transform
attribute which means special processing in the JS.

Furthermore, it's an extra interface in the DOM that would not have
been necessary (SVGLocatable and SVGTransformable could have been


On Sun, Feb 21, 2010 at 6:38 AM, Robert Longson <longsonr@gmail.com> wrote:
> Jeff,
> Perhaps because the outer SVG often has to fit inside some kind of
> rectangular space e.g. an embed or object or browser window. I don't think
> adding a <g> is so much of a hardship really is it?
> Best regards
> Robert.
Received on Sunday, 21 February 2010 14:29:23 UTC

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