Bugzilla

I'm thinking is this related to https://bugzilla.mozilla.org/show_bug.cgi?id=1506746?
The spec issue: https://github.com/w3c/csswg-drafts/issues/3290

> We return the values the animation is working on while the animation is going and that includes the endpoints per the definition in web animation

I just update this test in css/css-transforms/animation/translate-interpolation.html ([wpt.fyi](https://wpt.fyi/results/css/css-transforms/animation/translate-interpolation.html?label=experimental&label=master&aligned)), and it seems it's Chrome's bug, I think. In other words, I think we are correct because we have to promote none to 0px at 0%

I'm thinking is this related to https://bugzilla.mozilla.org/show_bug.cgi?id=1506746?
The spec issue: https://github.com/w3c/csswg-drafts/issues/3290

> We return the values the animation is working on while the animation is going and that includes the endpoints per the definition in web animation

I just updated this tests in css/css-transforms/animation/translate-interpolation.html ([wpt.fyi](https://wpt.fyi/results/css/css-transforms/animation/translate-interpolation.html?label=experimental&label=master&aligned)), and it seems it's Chrome's bug, I think. In other words, I think we are correct because we have to promote none to 0px at 0%

I'm thinking is this related to https://bugzilla.mozilla.org/show_bug.cgi?id=1506746?
The spec issue: https://github.com/w3c/csswg-drafts/issues/3290

> We return the values the animation is working on while the animation is going and that includes the endpoints per the definition in web animation

I just updated this tests in css/css-transforms/animation/translate-interpolation.html ([wpt.fyi](https://wpt.fyi/results/css/css-transforms/animation/translate-interpolation.html?label=experimental&label=master&aligned)), and it seems it's Chrome's bug, I think. In other words, I think Gecko is correct because we have to promote none to 0px at 0%

I'm thinking is this related to https://bugzilla.mozilla.org/show_bug.cgi?id=1506746?
The spec issue: https://github.com/w3c/csswg-drafts/issues/3290

> We return the values the animation is working on while the animation is going and that includes the endpoints per the definition in web animation

I just updated this tests in css/css-transforms/animation/translate-interpolation.html ([wpt.fyi](https://wpt.fyi/results/css/css-transforms/animation/translate-interpolation.html?label=experimental&label=master&aligned)), and it seems it's Chrome's bug. In other words, I think Gecko is correct because we have to promote none to 0px at 0%

I'm thinking is this related to https://bugzilla.mozilla.org/show_bug.cgi?id=1506746?
The spec issue: https://github.com/w3c/csswg-drafts/issues/3290

> We return the values the animation is working on while the animation is going and that includes the endpoints per the definition in web animation

I just updated this tests in css/css-transforms/animation/translate-interpolation.html ([wpt.fyi](https://wpt.fyi/results/css/css-transforms/animation/translate-interpolation.html?label=experimental&label=master&aligned)), and it seems it's Chrome's bug. In other words, I think Gecko is correct because we have to promote none to 0px at 0%.

I'm thinking is this related to https://bugzilla.mozilla.org/show_bug.cgi?id=1506746?
The spec issue: https://github.com/w3c/csswg-drafts/issues/3290

> We return the values the animation is working on while the animation is going and that includes the endpoints per the definition in web animation

I just updated this tests in css/css-transforms/animation/translate-interpolation.html ([wpt.fyi](https://wpt.fyi/results/css/css-transforms/animation/translate-interpolation.html?label=experimental&label=master&aligned)), and it seems it's Blink's bug. In other words, I think Gecko is correct because we have to promote none to 0px at 0%.