- From: Sylvain Galineau <galineau@adobe.com>
- Date: Mon, 11 Aug 2014 16:35:44 +0000
- To: Lea Verou <lea@verou.me>
- CC: "<www-style@w3.org>" <www-style@w3.org>
On Aug 10, 2014, at 9:38 PM, Lea Verou <lea@verou.me> wrote: > I think this is caused by the recent (?) changes in how @keyframes cascade. In the Keyframes section, the ED says: > > > To determine the set of keyframes, all of the values in the selectors are sorted in increasing order by time. If there are any duplicates, then the last keyframe specified inside the @keyframes rule will be used to provide the keyframe information for that time. There is no cascading within a @keyframes rule if multiple keyframes specify the same keyframe selector values. > > However, in the example right above it (example 2) the keyframes *do* cascade. Also, immediately after it: > > > If a property is not specified for a keyframe, or is specified but invalid, the animation of that property proceeds as if that keyframe did not exist. > > And earlier: > > > Issue: Need to describe what happens if a property is not present in all keyframes. > > Am I missing something or all all these excerpts conflicting? > > Btw Firefox seems to be the only one that does cascade keyframes, Chrome and IE do not [2]. Yikes, a commit of mine went wrong. I'll fix this today. Thanks!
Received on Monday, 11 August 2014 16:36:14 UTC