- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Sep 2018 01:47:07 +0000
- To: public-svg-issues@w3.org
> Per your comment above, looks like the behavior that would break D3 is either 1 or 2, and what you want is 3, right? Yes, I'm fine with spec'ing the Chrome 69 behavior. > There is currently no concept of "when needed" and it introduces a lot of complexity. I don't see how this different is from any other data format that converts values to support transitions. E.g., transitioning from `transform: rotate(1turn)` to `transform: scale(2)`, you transition via a matrix transform. To transition from `width: 100%` to `width: 10px` you transition via a `calc()` expression. So the answers re step timing functions and values at exact keyframe points would be "do whatever you do in those cases". > My experience is that adding complexity to interpolation code almost always creates more work over time Well, that much may be true… _________________________ A final option is just stick with the SVG 1 path animation rules (for now, anyway), and don't change any segment types to facilitate animations. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/svgwg/issues/321#issuecomment-423387674 using your GitHub account
Received on Friday, 21 September 2018 01:47:09 UTC