- From: Cameron McCormack <cam@mcc.id.au>
- Date: Fri, 6 Feb 2015 08:57:16 +1100
- To: Robert Longson <longsonr@gmail.com>
- Cc: www-svg@w3.org
Robert Longson: > What about number-optional-number? > > And viewBox numbers? > > If you're going to change things it should all be consistent shouldn't it? Yes that would be good. I am in the middle of trying to rationalise attribute parsing throughout the spec, and re-using the CSS parser (and using its metasyntax for describing valid values) where possible. For number-optional-number specifically, all uses of that have moved to the Filters spec, and that spec is currently written against SVG 1.1. If a second level of the Filters spec is started, we could base it on SVG 2 and use SVG 2’s attribute parsing rules. > There's also the arguments to transform to consider e.g. are you going to > allow transform="rotate(7-7-23)" or matrix, translate and scale arguments. I think that already works due to transform being a property now, and presentation attributes being parsed with the CSS parser. -- Cameron McCormack ≝ http://mcc.id.au/
Received on Thursday, 5 February 2015 21:57:43 UTC