- From: Antoine Quint via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Feb 2018 10:33:38 +0000
- To: public-css-archive@w3.org
graouts has just created a new issue for https://github.com/w3c/csswg-drafts: == [web-animations-1] getKeyframes() processing steps need updating after null composite == In KeyframeEffectReadOnly::getKeyframes(), we now say that `composite` should always be set with a default of `null` in the non-normative section: > **composite** > The keyframe-specific composite operation used to combine the values specified in this keyframe with the underlying value. > > This member will be null if the composite operation specified on the keyframe effect is being used. However, in the (normative) processing steps below, we say: > 2. Set offset, computedOffset, easing members of output keyframe to the respective values keyframe offset, computed keyframe offset, and keyframe-specific timing function of keyframe. > > 3. If keyframe has a keyframe-specific composite operation, set composite to that value. I believe we should get rid of 3. and update 2. to read: > 2. Set offset, computedOffset, easing, composite members of output keyframe to the respective values keyframe offset, computed keyframe offset, keyframe-specific timing function and keyframe-specific composite operation of keyframe. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2289 using your GitHub account
Received on Thursday, 8 February 2018 10:33:50 UTC