- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Tue, 27 Oct 2020 00:41:54 +0000
- To: public-css-archive@w3.org
The important distinction here is between (specified) keyframe offsets and computed keyframe offsets. In this procedure, computed keyframe offsets are generated purely in order to merge corresponding elements from parallel arrays into the same keyframes. They are not used when determining if keyframes are sorted by offset or not, and don't interact with the specified offsets at all. For all intents and purposes, the computed keyframe offsets are ignored after keyframes are merged (they will be recalculated when the computed keyframes are later generated). > > Assign each value in offsets to the keyframe offset of the keyframe with corresponding position in processed keyframes until the end of either sequence is reached. > > The result is now `[1, 0.5, 1]`, which should trigger the `TypeError`. The result here will be that the first keyframe gets an offset of `1` while all the other keyframes are untouched and have an offset of `null`. Later, when the computed keyframes are generated (e.g. by calling `getKeyframes()`), the computed offsets will be calculated. -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5664#issuecomment-716904140 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 27 October 2020 00:41:56 UTC