- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Sep 2016 06:51:32 +0000
- To: public-css-archive@w3.org
For the following arrangement:
```css
div {
animation-name: spin;
animation-duration: 2s;
animation-iteration-count: 3;
animation-delay: -3s;
}
```
Firefox:
```log
animationstart (3)
animationiteration (3)
animationiteration (4)
animationend (6)
```
Chrome:
```log
animationstart (3)
animationiteration (4)
animationend (6)
```
Edge:
```log
animationstart (3)
animationiteration (4)
animationend (6)
```
Safari:
```log
animationstart (0)
animationiteration (4)
animationend (6)
```
Test case: https://jsfiddle.net/gmjg2k3b/1/
That suggests that:
1. Changing `elapsedTime` to report the actual elapsed time would
require changing all the browsers
2. There might be wiggle room for changing the value of `elapsedTime`
since at least for the case of a negative delay, Safari does not
follow the spec.
That said, I think I'll just go ahead and spec approach a
(reflect-the-current-iteration) from the previous comment.
--
GitHub Notification of comment by birtles
Please view or discuss this issue at
https://github.com/w3c/csswg-drafts/issues/68#issuecomment-246591329
using your GitHub account
Received on Tuesday, 13 September 2016 06:51:41 UTC