- From: Simon Fraser <smfr@me.com>
- Date: Wed, 23 Sep 2015 20:08:07 -0700
- To: "L. David Baron" <dbaron@dbaron.org>
- Cc: www-style@w3.org, Cameron McCormack <cam@mcc.id.au>
> On Sep 23, 2015, at 3:58 pm, L. David Baron <dbaron@dbaron.org> wrote: > > I was looking at an issue in css-animations with Cameron, and > spotted something in the animations spec that seemed wrong to me. > It went back to this edit: > https://hg.csswg.org/drafts/rev/685f66d955ec > which introduced text saying that an 'animation-timing-function' > within a keyframe rule would apply until the next keyframe rule that > had another animation-timing-function declaration. Previously I'd > have interpreted the spec as implying that it was until the next > keyframe for the property being animated, whether or not that > keyframe has an animation-timing-function declared. > > I'm not sure why this edit was made. However, based on this test: > http://dbaron.org/css/test/2015/animation-timing-function > it disagrees with all implementations that I've tested (Firefox, > Chrome, IE11 [1]). Given that the edit was intended as a > clarification, I plan to change the spec to re-clarify things in the > other direction, i.e., to match the way all implementors that I'm > aware of had interpreted the old wording. This seems fine; Safari agrees with the Firefox behavior: the lower pair of blue boxes in your testcase move in sync. Simon
Received on Thursday, 24 September 2015 03:08:39 UTC