- From: Sam Atkins via GitHub <sysbot+gh@w3.org>
- Date: Mon, 25 Sep 2023 14:02:07 +0000
- To: public-svg-issues@w3.org
I have some additional questions related to [the fix-up algorithm](https://svgwg.org/svg2-draft/types.html#presentation-attribute-css-value) in particular: 1. After parsing the `<number>`, how should it be interpreted? I assume it should become a `<length>` in `px`, or an `<angle>` in `deg`, similar to the CSS unitless-length quirk? 2. How do [range restrictions](https://www.w3.org/TR/css-values-4/#numeric-ranges) on the `<angle>`s or `<length>`s apply to these `<number>`s? 3. Just specifying these as accepting `<number>` means implicitly allowing any function notation that evaluates to `<number>`. Is that intentional? eg: `calc(42 * 3)` is valid as an `<angle>` or `<length>` under the current description. 4. "Replace all instances of..." seems to mean that functions like `atan(30)` would be valid that should only accept `<angle>` as a parameter. My impression is that this is supposed to behave like the unitless-length quirk, but some CSS definitions have changed in the mean time and the spec no longer matches that intention. -- GitHub Notification of comment by AtkinsSJ Please view or discuss this issue at https://github.com/w3c/svgwg/issues/792#issuecomment-1733774643 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 25 September 2023 14:02:09 UTC