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

Re: Promoting more SVG attributes into properties

From: Dirk Schulze <dschulze@adobe.com>
Date: Fri, 25 Jan 2013 07:12:20 -0800
To: "Tab Atkins Jr." <jackalmage@gmail.com>
CC: Cameron McCormack <cam@mcc.id.au>, www-svg <www-svg@w3.org>
Message-ID: <57592F7A-6DC6-4F4C-9127-A2B52627D344@adobe.com>

On Jan 24, 2013, at 5:03 PM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote:

> On Thu, Jan 24, 2013 at 4:50 PM, Cameron McCormack <cam@mcc.id.au> wrote:
>> Tab, In your mail to www-style you mention points and then defining it to
>> take [ <length> | <percentage> ]#.  points, as well as x/y/dx/dy on text
>> content elements, currently use comma-wsp separation (white space or comma
>> with optional white space).  Is it deliberate that the property would
>> require commas, whereas the presentation attribute would not?  I haven't
>> thought about it hard enough to have an opinion on whether that is the right
>> way to go.
> Ugh, I forgot about that.  I guess we could define the grammar as
> "[<length> | <percentage>] [ ,? [<length> | <percentage>] ]*".  I'd
> prefer if we were indeed able to switch over to CSS's conventions, but
> if not, the grammar is doable.

It might be ok to require commas on CSS. That is what we do on basic shapes (polygon() function ) for exclusions and clip-path. Alternatively we relax the syntax there as well.


> ~TJ
Received on Friday, 25 January 2013 15:12:54 UTC

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