- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Jul 2016 16:31:56 +0000
- To: public-svg-issues@w3.org
Thanks for all the comments @nikosandronikos! Re x/y/width/height as simple attribute versus presentation attributes for the corresponding geometric properties: The issue is that it can't be described with either the CSS inheritance model or with a container model. The used value for the "child" (`<svg>` or `<symbol>`) element is the value set on the "parent" (`<use>`), _iff_ the parent has a non-auto value, otherwise use the child's own computed value (or if it's also auto, use 100%). There's no way to define that with user agent stylesheet rules, or with rules for the conversion of `auto` into lengths. However, at this point I'm inclined to make them presentation attributes anyway. One way or the other (simple attributes or presentation), we end up with special over-ride rules where the used value for the `<svg>`/`<symbol>` isn't based on their computed value. So we might as well add in the convenience of being able to set the values on the `<use>` with CSS. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/svgwg/pull/206#issuecomment-234004527 using your GitHub account
Received on Wednesday, 20 July 2016 16:32:03 UTC