W3C home > Mailing lists > Public > www-svg@w3.org > June 2005

Re: SVG12: 'display' trait

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Tue, 07 Jun 2005 12:34:55 +0200
To: "Ola Andersson" <Ola.Andersson@ikivo.com>
Cc: <www-svg@w3.org>, "WG SVG" <w3c-svg-wg@w3.org>
Message-ID: <42b8753f.80243531@smtp.bjoern.hoehrmann.de>

* Ola Andersson wrote:
>We've now added the following wording to the 'display' trait
>The table [referring to the 'display' entry in the table that
>you referred to] shows the recommended values in the SVG context.
>However, the list of values that can be set is the same as the
>list of valid values for the 'display' property in markup (see
>the Controlling visibility section). In the SVG context, the
>returned value for 'display' is limited to 'inline' and 'none'
>because implementations further normalize the computed value.

Where does the draft require implementations to normalize computed
property values? The draft does allow implementations to normalize
attribute values so e.g.

  <g fill="red"> and <g fill="#ff0000">

may be considered equivalent for all purposes of SVG processing
(even though that's not really well-defined in the draft) but I
could not find the requirement the new text refers to. The
getAttributeNS() method does not operate on this value space, so
do I understand correctly that even if getTrait behaves as you
describe, for

  <g display="block">

getAttributeNS(null, "display") would return "block" and "block"
is the computed (base) property value? Are there other properties
for which the computed value is "normalized"?
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Tuesday, 7 June 2005 10:34:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:54:06 UTC