- From: Erik Dahlstrom <ed@opera.com>
- Date: Tue, 24 Aug 2010 15:39:16 +0200
- To: public-svg-wg@w3.org
On Tue, 24 Aug 2010 06:14:56 +0200, Cameron McCormack <cam@mcc.id.au> wrote: > SVG Working Group Issue Tracker: >> The definition of <image> in SVG 1.1, under "Presentation Attributes" >> list the various 'stroke' attributes. >> >> http://www.w3.org/TR/SVG/struct.html#ImageElement >> >> I think this is a change from SVG 1.1. We should either remove them, >> or change SVG to allow stroke. > > One of the changes we made in Second Edition was to make all > presentation attributes be valid to specify on all stylable elements. > > http://dev.w3.org/SVG/profiles/1.1F2/publish/changes.html#WholeDocument > > The blue element summary boxes list the attributes that can be validly > specified on the elements. This is not to say that it will have an > effect on the rendering. It will have an effect on the element’s > computed style, however. > > (There is after all no way to prevent the stroke properties from being > set on an <image> due to a style="" attribute or a matching selector > from a style sheet. These will still have no effect on the rendering of > the element, but will be reflected in the element’s computed style if > looked up with script.) I think Cameron's reasoning makes sense. It's quite clear from the 'stroke' property definition that it only "applies to" certain elements (<image> isn't one of them). IMHO the spec we have right now is much more readable than the DTD (or DTD snippets), which was what we had before. Cheers /Erik -- Erik Dahlstrom, Core Technology Developer, Opera Software Co-Chair, W3C SVG Working Group Personal blog: http://my.opera.com/macdev_ed
Received on Tuesday, 24 August 2010 13:39:50 UTC