- From: Eric Seidel <eseidel@apple.com>
- Date: Mon, 6 Mar 2006 02:11:51 -0800
- To: Chris Lilley <chris@w3.org>
- Cc: www-svg@w3.org
Perfect. I am satisfied. Thanks. -eric On Mar 6, 2006, at 2:05 AM, Chris Lilley wrote: > Hello www-svg, > > Eric Seidel <eseidel@apple.com> wrote: > >> I noticed this evening, that given the current wording of the spec, >> this could produce different behavior in different user agents >> depending on what CSS properties the user agent supported. > > Yes. A case in point would be a compound document by inclusion (CDI) > implementation, where width and height are CSS properties and also > they > are SVG attributes. As you note, the case for auto would give > different > behaviour for a CDI implementation compared to a strictly SVG one. > Both > can be animated, in this case, by explicitly specifying either css or > xml as values of attributeType. > >> The working group might consider disambiguating this section of the >> spec by specifying if all CSS properties that the user agent supports >> are to be considered in this calculation or only CSS properties >> defined by the SVG spec. > > We agree and have disambiguated the text as follows: > > The implementation must first search through its list of > supported CSS > properties for a matching property name (all properties supported by > the implementation, not just those defined by SVG), and if none is > found, search the default XML namespace for the element. > > Please let us know shortly if this does not satisfy your comment. > > -- > Chris Lilley mailto:chris@w3.org > Chair, W3C SVG Working Group > W3C Graphics Activity Lead > Co-Chair, W3C Hypertext CG >
Received on Monday, 6 March 2006 10:11:57 UTC