- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Jun 2024 16:41:28 +0000
- To: public-svg-issues@w3.org
emilio has just created a new issue for https://github.com/w3c/svgwg: == Define path interpolation when relative and absolute segment types are used. == https://svgwg.org/svg2-draft/paths.html says how to interpolate paths: > For animation, two [d](https://svgwg.org/svg2-draft/paths.html#DProperty) property values can only be interpolated smoothly when the path data strings contain have the same structure, (i.e. exactly the same number and types of path data commands which are in the same order). If an animation is specified and the lists of path data commands do not have the same structure, then the values must be [interpolated](https://drafts.csswg.org/web-animations/#animation-interpolation) using the [discrete](https://drafts.csswg.org/web-animations/#discrete-animation-type-section) animation type. However browsers support interpolating relative with non-relative paths, and currently behavior diverges across browsers... https://wpt.fyi/results/svg/animations/animate-path-animation-Mm-Aa-Z.tentative.html?label=experimental&label=master&aligned What is the correct behavior? Should paths always be normalized (absolutized) before interpolation? Or should paths try to preserve relativeness, and if so what's the right way to deal with mismatches? Please view or discuss this issue at https://github.com/w3c/svgwg/issues/947 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 21 June 2024 16:41:28 UTC