W3C home > Mailing lists > Public > www-svg@w3.org > November 2013

Re: 'stroke' shorthand

From: Dr. Olaf Hoffmann <Dr.O.Hoffmann@gmx.de>
Date: Wed, 13 Nov 2013 11:58:58 +0200
To: www-svg@w3.org
Message-Id: <201311131058.58384.Dr.O.Hoffmann@gmx.de>
Dirk Schulze:
...
>That also means that in the following example, the shorthand property resets 
>all previously set properties according to the regulations of the CSS WG:

>stroke-width: 2px;
>stroke-linecap: round;
>stroke-linejoin: round;
>stroke-dasharray: 4px 3px;
>stroke: green;

>stroke-width would be reset to 1px, stroke-linecap to butt stoke-linejoin to 
>miter and stroke-dasharray to none, because stroke (the shorthand) is set 
>after these properties.

Such a behaviour seems to be of limited use and will typically not
meet what authors want ...

>This makes property handling significantly different in SVG and potentially 
>break existing content.

This is reason enough not to give such a construct the name of an already
existing attribute/property ;o)

Currently SVG has no presentation attributes for CSS-shorthands at all.
If one starts to introduce it, because the order attributes are noted does not
matter, it causes new problems.
stroke as fill is already overloaded now - the value structure is already
toooo complex - causing trouble concerning for example proper implementations
of SMIL animation - one thing one can learn from this is - keep
attribute/property values simple and do not mix different animation types 
in such values. 

Because in general the property/CSS notation is anyway of limited use 
for good SVG documents or only for alternative views of the same document,
typically one will not need such a shorthand at all.
Or to avoid conflicts, one could call it 'stroke-shorthand', but obviously 
not 'stroke', the same applies for example for 'fill' ...

Olaf
Received on Wednesday, 13 November 2013 09:59:31 UTC

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