- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Apr 2025 14:27:17 +0000
- To: public-css-archive@w3.org
@kevers-google I believe the spec is not correct here. We do implement the notion of at progress timeline boundary, however the way we implemented it is such that only the maximum scrolling position is at the progress timeline boundary, not 100% of a viewtimeline. This particular exception was explicitly added because being at 100% of the scroll position is a common edge case that developers would overlook and since there can be no animation that starts after it there is no risk of having two animations active where one starts at the time the previous one ends. TLDR, we should update the spec to correctly explain this. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12134#issuecomment-2839144119 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 29 April 2025 14:27:18 UTC