Re: [svg2] computed value for <length>


> On Mar 3, 2015, at 1:42 PM, Erik Dahlström <ed@opera.com> wrote:
> 
> Hello,
> we have added the 'computed value' field in the property definitions in svg2 (compared to svg 1.1). It seems we've mostly added these as "specified value". For consistency with css (and implementations to some degree) I think we should make <length> use the absolute length as the computed value.

You probably mean computed style which should be the specified value. The computed value is usually not part of the definition table. IIRC we don’t need to specify the computed value because this is done by a CSS spec.

Greetings,
Dirk

> 
> Here is the complete list of properties I found that currently use 'specified value' for <length>:
> 
>  cx
>  cy
>  r
>  rx
>  ry
>  stroke-width
>  stroke-dasharray
>  stroke-dashoffset
>  stroke-dashcorner
>  x
>  y
> 
> Proposed:
> The computed length of the above properties should be the absolute length or percentage (as applicable).
> 
> Open question: how should units be handled (wrt serialization and interpolation while animating)? Implementations differ a bit here. Is this aspect currently defined anywhere?
> 
> I also noticed that stroke-dasharray is defined as "<length> | <percentage> | <number>", where most other length-properties in svg2 used only "<length> | <percentage>". Is this intentional or not?
> 
> 
> -- 
> Erik Dahlstrom, Web Technology Developer, Opera Software
> Co-Chair, W3C SVG Working Group
>

Received on Tuesday, 3 March 2015 13:31:27 UTC