- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Sun, 27 May 2018 16:51:51 +0000
- To: public-css-archive@w3.org
My thoughts: - Having an existing transformation suddenly disappear at the start/end of a transform is very bad behavior. - Ideally, the values would be interpolated [according to the usual algorithm](https://drafts.csswg.org/css-transforms/#interpolation-of-transforms), with `px`/`deg` units serialized in. - If that is not possible for implementations, then the entire attribute should be condensed into a single `matrix` transformation, and that used for interpolation. The 3-value rotate function is a little trickier. According to the current spec text, it is one of the [primitive transform functions](https://drafts.csswg.org/css-transforms/#transform-primitives), and the simple rotate function should be upgraded to the 3-value form and then transitioned. But since the 3-value form is legacy-only, I think it would be acceptable to change the spec so that the 3-value form is treated as its own unique function that doesn't transition to any other rotate form (i.e., forcing the transition to use the cumulative matrices). (PS, @dirkschulze I changed the Agenda+ label, assuming you weren't intentionally deferring discussion until the August F2F.) -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2684#issuecomment-392346848 using your GitHub account
Received on Sunday, 27 May 2018 16:51:53 UTC