W3C home > Mailing lists > Public > public-svg-wg@w3.org > January to March 2009

Re: ISSUE-2210 (svgtransform-matrix-liveness): Define liveness of SVGTransform.matrix [SVG Full 1.1]

From: Cameron McCormack <cam@mcc.id.au>
Date: Thu, 5 Feb 2009 15:26:55 +1100
To: public-svg-wg@w3.org
Message-ID: <20090205042655.GE2051@arc.mcc.id.au>

SVG Working Group Issue Tracker:
> Copied from <http://www.w3.org/Graphics/SVG/Group/track/issues/12>:
> > http://lists.w3.org/Archives/Member/w3c-svg-wg/2004AprJun/1137.html
> 
> We already have an erratum stating that assigning calling
> SVGTransform.setMatrix() does not cause the SVGTransform object to
> adopt the matrix; it just makes a copy of it. We don't define whether
> modifying the components of the existing SVGTransform.matrix affects
> the transform item, or whether the returned SVGMatrix is live at all.

So in fact we have an erratum that clarifies whether SVGMatrix component
values update when the SVGTransform is updated:

  http://www.w3.org/2003/01/REC-SVG11-20030114-errata#mention-live-values

However it doesn’t say if assigning to those components is allowed.
Note that assigning to the type and angle attributes is not allowed
(since they are readonly), so it could be argued that it would be
consistent to disallow this.  OTOH, those components aren’t readonly
attributes, so perhaps they should be expected to have some effect when
modified.

-- 
Cameron McCormack ≝ http://mcc.id.au/
Received on Thursday, 5 February 2009 04:27:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 5 February 2009 04:27:46 GMT