- From: Doug Schepers <doug.schepers@vectoreal.com>
- Date: Wed, 4 Jan 2006 00:02:36 -0500
- To: <www-svg@w3.org>
- Cc: "'Dean Jackson'" <dino@w3.org>, "'Bjoern Hoehrmann'" <derhoermi@gmx.net>, "'Ian Hickson'" <ian@hixie.ch>
Hi, folks- Dean Jackson wrote: | | If we can have a solution where authors get to use stroke-width="4" | in XML content and are required to use "{stroke-width: 4px}" in | stylesheets, then I'm happy. I would be happier if CSS hadn't | required units on <length>s, but I have a sneaking suspicion that | that won't change. | | [of course I mean requiring units in CSS stylesheets, not that all | objects must be stroked with four pixels :] | | BTW - I'm not speaking for the SVG WG here. I'm also not speaking for the SVG WG (nor for Dean), but I share Dean's view. I'm not sure exactly how this differs from what already is in the SVG Spec, so I don't really see what the fuss is about. Ian Hickson wrote: | | * Remove the requirement that SVG places on CSS parsers to | accept <length>s that are just <number>s. Is this actually in the Spec? I found this passage [1]: "SVG shares the following facilities with CSS and XSL: [...] "Allowable data types. (The normative reference is [CSS2 syntax and basic data types]), with the exception that SVG allows <length> and <angle> values without a unit identifier. See Units.)" However, it's not clear to me that this dictates any such requirement on CSS parsers; it could just as easily be referring to the data types that SVG itself allows in its attributes. In any case, I personally agree that it should be clarified in the Spec that property values must follow the constraints of CSS data types, while attribute values can remain unitless (as is appropriate in the SVG context). [1] http://www.w3.org/TR/SVG/styling.html#CSSSVGUseOfCSS Regards- Doug doug.schepers@vectoreal.com www.vectoreal.com ...for scalable solutions.
Received on Wednesday, 4 January 2006 05:02:46 UTC