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

Re: How to parse SVG Fragment Identifiers

From: Daniel Holbert <dholbert@mozilla.com>
Date: Mon, 27 Aug 2012 12:33:42 -0700
Message-ID: <503BCB96.6080807@mozilla.com>
To: Cameron McCormack <cam@mcc.id.au>
CC: Robert Longson <longsonr@gmail.com>, www-svg@w3.org
On 08/26/2012 11:56 PM, Cameron McCormack wrote:
> Robert Longson:
>> Question 1. What is the syntax for AspectParams?
>>
>> Lets say you want to set preserveAspectRatio="xMinYMin slice"
>>
>> We have this sentence in the specification: "Spaces are not allowed in
>> fragment specifications; thus, commas are used to separate numeric
>> values within an SVG view specification"
> 
> As Olaf pointed out, you can write %20 for a space (and in many
> situations e.g. in HTML you can actually just include a space in an <a
> href> attribute), so I think we should just continue requiring a space
> (after decoding of the fragment) and not allow a comma there.

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?

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.

~Daniel
Received on Monday, 27 August 2012 19:34:10 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:52 GMT