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

Re: How to parse SVG Fragment Identifiers

From: Dirk Schulze <dschulze@adobe.com>
Date: Mon, 27 Aug 2012 16:39:28 -0700
To: Cameron McCormack <cam@mcc.id.au>
CC: Daniel Holbert <dholbert@mozilla.com>, Robert Longson <longsonr@gmail.com>, "www-svg@w3.org" <www-svg@w3.org>
Message-ID: <EAE2E80B-81FE-4734-85FF-CCC26D0D86FF@adobe.com>
Also, we should try to be as consistent with Madia fragments[1]. This is necessary for CSS and HTML integration.


[1] http://www.w3.org/TR/media-frags/

On Aug 27, 2012, at 4:27 PM, Cameron McCormack <cam@mcc.id.au> wrote:

> Daniel Holbert:
>> But the same logic would apply to viewBox -- you could easily use %20
>> instead of spaces there, too, but the spec says you have to use commas.
>>  Should we nix the special-case comma syntax there as well?
> Hmm.  Have you tested other implementations to see if they accept commas 
> inside viewBox()?
>> I'd argue we should mandate the same can't-use-spaces-workaround across
>> all of the components of svgView().  I don't particularly care whether
>> we use %20 or commas (or either?), but I think we should be consistent
>> on that.
> I agree consistency here is preferable.
Received on Monday, 27 August 2012 23:40:02 UTC

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