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

Re: computed values of properties

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Sat, 19 May 2012 08:34:11 -0700
Message-ID: <CAAWBYDAG5_LCWOH68MRaXzNfJVKNWittwNhCv58tnFTGA==bmQ@mail.gmail.com>
To: "L. David Baron" <dbaron@dbaron.org>
Cc: Cameron McCormack <cam@mcc.id.au>, SVG public list <www-svg@w3.org>
On Sat, May 19, 2012 at 4:39 AM, L. David Baron <dbaron@dbaron.org> wrote:
> On Saturday 2012-05-19 15:02 +1000, Cameron McCormack wrote:
>> 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.
>
> One thing to beware of is that the getComputedStyle() method
> actually returns used values, which are a significantly different
> concept from computed values in many cases.

Except when it *does* return the computed value.  It only returns the
used value for a specific list of 2.1 properties, right?  (Because at
the time the CSSOM was written, CSS2 had a different definition of
"computed value" that maps more closely to today's notion of "used
value".

~TJ
Received on Saturday, 19 May 2012 15:35:01 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:51 GMT