- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Tue, 30 Jun 2020 12:42:07 +0000
- To: public-css-archive@w3.org
Thanks for the clarification, I agree this is probably more in line with the developer intention, however I think this isn't equivalent to [100, 250, 250, 400], because it loses the information that 250 is only 2/3 of the way to the second / third keyframe. Perhaps we should keep the conflicting scroll offsets in the calculated offsets and define a procedure for determining the current offset which applies this logic, e.g. something like If offset i + 1 is less than offset i, find the first offset j which is greater than or equal to offset i. If the scroll offset falls between offset i and offset j then the resulting animation offset uses the pair [i, i + 1] or [j - 1, j] whichever of i or j is closer to the current position. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4912#issuecomment-651765953 using your GitHub account
Received on Tuesday, 30 June 2020 12:42:08 UTC