- From: Stephen McGruer via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Sep 2019 14:45:33 +0000
- To: public-css-archive@w3.org
Came across this whilst porting more interpolation tests from Blink internal to WPT. A similar problem exists for how many axes should be included, e.g. the following failures from Firefox: ``` FAIL CSS Transitions: property <scale> from [26 17 9] to [2 1] at (1) should be [2 1] assert_equals: expected "2 1 " but got "2 1 1 " FAIL CSS Transitions: property <scale> from [1] to [10 -5 0] at (0) should be [1] assert_equals: expected "1 " but got "1 1 1 " ``` Blink is short-circuiting the interpolation at 0%/100%, so we don't expand (say) `2 1` to `2 1 1`, and thus output just two number (which is a valid serialization). Would be nice to specify what happens both here and in the original 'none' case (maybe just by spec-ing in web-animations that interpolation can't be short-circuited, though that would nix some of our optimizations - not sure how important they are atm). -- GitHub Notification of comment by stephenmcgruer Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3290#issuecomment-535058011 using your GitHub account
Received on Wednesday, 25 September 2019 14:45:34 UTC