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

Re: ISSUE-2255 (useCurrentView-modification): Effect of modifying SVGSVGElement::useCurrentView unclear [SVG Full 1.1]

From: Cameron McCormack <cam@mcc.id.au>
Date: Mon, 20 Apr 2009 13:57:13 +1000
To: public-svg-wg@w3.org
Message-ID: <20090420035713.GC15070@arc.mcc.id.au>
Cameron McCormack:
> > It is unclear what the effect of modifying the
> > SVGSVGElement::useCurrentView attribute should be, especially since it
> > reflects the state of the "inital view", i.e. just when the document
> > is first displayed. Perhaps the attribute should be read only? Also,
> > it's not clear when the NO_MODIFICATION_ALLOWED_ERR DOMException would
> > be thrown, since useCurrentView doesn't correspond to a DOM attribute.
> 
> Similarly for SVGSVGElement::currentScale — since this IDL attribute
> doesn’t correspond to an attribute node on the <svg> element, it doesn’t
> make sense to say that a NO_MODIFICATION_ALLOWED_ERR would be raised “on
> an attempt to change the value of a readonly attribute”.

I’ve added the errata for these now, for ACTION-2510:

  http://dev.w3.org/SVG/profiles/1.1F2/errata/errata.xml#usecurrentview-should-be-read-only
  http://dev.w3.org/SVG/profiles/1.1F2/errata/errata.xml#currentscale-should-not-throw

-- 
Cameron McCormack ≝ http://mcc.id.au/
Received on Monday, 20 April 2009 03:58:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 20 April 2009 03:58:01 GMT