- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Thu, 20 Sep 2018 19:23:49 +0000
- To: public-svg-issues@w3.org
> I don't understand, how would it break? Could you put an example? D3 animation of complex types like path strings works by breaking the string into numbers versus text, and then interpolating the numbers while instantly switching the strings. When applied to a style property, it uses the `getComputedStyle()` value as the starting point; when applied to an attribute, it uses the current attribute value. Example, using first an attribute format and then a style format: https://codepen.io/AmeliaBR/pen/dqawQQ?editors=1010 Note that both currently work in Chrome (v69), because the get computed style is only normalizing as I suggested above (inserting the omitted `l` commands, and adding whitespace instead of commas around all coordinates). > Well, yeah, that means that we need to use much more memory to store paths instead of sharing them, which is not great. How so? Presumably the author is being consistent in using either relative or absolute commands. The upgrading would only happen when generating intermediate values in an animation, and you'd need to generate unique paths for that case, anyway. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/svgwg/issues/321#issuecomment-423302694 using your GitHub account
Received on Thursday, 20 September 2018 19:23:51 UTC