W3C home > Mailing lists > Public > www-svg@w3.org > May 2012

Re: computed values of properties

From: Cameron McCormack <cam@mcc.id.au>
Date: Sat, 19 May 2012 16:05:08 +1000
Message-ID: <4FB73814.7050904@mcc.id.au>
To: Dirk Schulze <dschulze@adobe.com>
CC: SVG public list <www-svg@w3.org>
Cameron McCormack:
>> One thing that the SVG 1.1 spec is missing is a definition of how
>> the computed values of properties are determined.  For example I
>> notice just now that stroke-width in Gecko will compute an em
>> length down to a px value and keep percentage values as specified,
>> while in WebKit and Opera both values are kept as specified.  As I
>> go about reformatting our property definitions to match CSS specs,
>> I will put something hopefully reasonable in for the "Computed
>> value" lines, which I would then appreciate review of.

Dirk Schulze:
> I don't understand what you mean. The presentation attribute is a
> author style sheet. So there should be the same rules like for any
> other author style sheet. That doesn't need to get defined
> separately.  I think that is why SVG defines the attribute as author
> style sheet. If I miss a point, can you add an example please?

I just mean for the property definition, not the presentation 
attributes.  (Well, this is independent of whether you've specified it 
as a presentation attribute or in a style sheet.)  This is just for 
properties that are defined in SVG that don't exist in other CSS specs, 
like stroke-width, by the way.  We need to write something for "Computed 
value" in the property definition box, like:


so that you know what you get if you call getComputedStyle on the 
element, and what value gets inherited.
Received on Saturday, 19 May 2012 06:05:49 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:28 UTC