- From: guest271314 via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Apr 2018 17:05:44 +0000
- To: public-css-archive@w3.org
guest271314 has just created a new issue for https://github.com/w3c/csswg-drafts: == [web-animations-1] Should calling `reverse()` set `effect.timing.direction` to `"reverse"`? == * please tag the issue title with the spec's shortname, like `[css-foo]` * please link to the spec section you're talking about, or at least the spec https://drafts.csswg.org/web-animations/#directed-progress; https://drafts.csswg.org/web-animations/#dom-animation-reverse At Chromium 65, calling `reverse()` does not appear to change the value of `effect.timing.direction`. The specification does not explicitly state that `effect.timing.direction` is changed based on the current or previous direction of the animation. Should calling `reverse()` set `effect.timing.direction` to `"reverse"`? How to determine the current or previous (is paused) direction of an animation? . Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2543 using your GitHub account
Received on Wednesday, 11 April 2018 17:05:50 UTC