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

Re: 'stroke' shorthand

From: Cyril Concolato <cyril.concolato@telecom-paristech.fr>
Date: Mon, 18 Nov 2013 16:52:34 +0100
Message-ID: <528A37C2.7080806@telecom-paristech.fr>
To: www-svg@w3.org
Le 13/11/2013 03:00, Dirk Schulze a écrit :
> Hi,
>
> Currently we have the following properties with the introducing term ’stroke’ and their definitions:
>
> stroke:    <paint> with <paint> = none | <color> <icccolor>? | <funciri> [ none | <color> <icccolor>? ]
> stroke-width:    <length> | <precentage>
> stroke-linecap:    butt | round | square
> stroke-linejoin:    miter | round | bevel
> stroke-miterlimit:    <miterlimit> with <miterlimit> = <number> (number must be >= 1)
> stroke-opacity:    <opacity-values> with <opacity-values> = <number>
> stroke-dasharray:    none | <dasharray> with <dasharray> = [ <length> | <percentage> ] [[,]? <length> | <percentage>]*
> stroke-dashoffset:    <length> | <precentage>
>
> In previous discussions, we talked about following the CSS rules regarding shorthands. Two points I want to discuss taking the example of ‘stroke’ and the other of the former listed properties as defined in SVG11[1]:
>
> 1) The CSS WG uses the shorter initial part of a term as a so called "shorthand property".
My 2 cents: couldn't you simply use 'stroke-shorthand' (or alike) to 
define the short hand instead of redefining 'stroke'?

Cyril

-- 
Cyril Concolato
Maître de Conférences/Associate Professor
Groupe Multimedia/Multimedia Group
Telecom ParisTech
46 rue Barrault
75 013 Paris, France
http://concolato.wp.mines-telecom.fr/
Received on Monday, 18 November 2013 15:53:04 UTC

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