- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 Oct 2017 21:32:31 +0000
- To: public-svg-issues@w3.org
OK, sorry. I was getting ["used values" confused with "actual values"](https://drafts.csswg.org/css-cascade-4/#used) in CSS's complicated series of value-resolution terms. For any API that is reporting a used value where values are resolved to px for `width` and `height` on CSS layout boxes, I would expect the same for any SVG elements where the properties apply. Consistency should outweigh theoretical purity. I suspect it was overlooked in the initial geometry property implementations, so they are still coded as if `width` and `height` don't apply to the element & therefore there is no "used value". The next question is, for the _other_ SVG geometry properties, should they be explicitly made to match the `width`/`height` behavior (resolve to px), or should they report the computed value (with units, percentage, or auto)? -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/svgwg/issues/349#issuecomment-335296571 using your GitHub account
Received on Monday, 9 October 2017 21:32:20 UTC