- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 Oct 2020 19:08:27 +0000
- To: public-css-archive@w3.org
cdoublev has just created a new issue for https://github.com/w3c/csswg-drafts:
== [web-animations-1] Object-form keyframe with offset: 1 ==
Hello,
I'm struggling to understand why a keyframe like `{ offset: 1, opacity: [0, 1, 0] }` doesn't trigger (in Chrome/Firefox) the `TypeError` described in step 6 of the [procedure to process a keyframes argument](https://drafts.csswg.org/web-animations-1/#process-a-keyframes-argument), ie:
> If processed keyframes is not loosely sorted by offset, throw a TypeError and abort these steps.
Allow me to sum up the meaningfull steps from this procedure:
> For each value in property [opacity] values:
> 1. Let k be a new keyframe with a null keyframe offset.
> 2. Add the property-value pair to k.
> 3. Append k to property keyframes.
> Apply the procedure to compute missing keyframe offsets to property keyframes
The result of the computed offsets must be `[0, 0.5, 1]`.
> 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`.
Am I misunderstanding/missing something that would explain why it is not?
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5664 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 26 October 2020 19:08:29 UTC