W3C home > Mailing lists > Public > public-fxtf-archive@w3.org > October 2017

Re: [fxtf-drafts] [motion] Blink shipping animation of offset-path path strings

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Thu, 05 Oct 2017 00:14:46 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issue_comment.created-334324740-1507162472-sysbot+gh@w3.org>
B should be preserved, I think. Animating between `B 0 H 100` and `B 90 H 100` gives dramatically different results if you do or don't normalize away the Bs. If you keep the Bs, you get a circular sweep, with a length-100 line turning thru 90 degrees. If you normalize them away (to `L 100 0` and `L 0 100`, I think), you get a line where the endpoint goes straight from the start to finish, and the line changes length from 100 to ~71 back to 100 at the end.

In real-world use-cases, B is extraordinarily useful for rotating a path - rather than screwing around with transforms, you can just define the path once, then prepend a B to put it at the angle you want. This also helps a lot when a particular path segment uses easy-to-define numbers when axis-aligned, but requires trig to figure out the endpoints when rotated - instead, just do it axis-aligned and prepend a B.  In both of these situations, normalizing away the B would look pretty bad.

GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/225#issuecomment-334324740 using your GitHub account
Received on Thursday, 5 October 2017 00:14:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:50:21 UTC