- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Mon, 11 Sep 2023 16:46:27 +0000
- To: public-css-archive@w3.org
> in my mind the “inactive” would happen only when the _range_ is such that its _length_ is zero, thus 0% and 100% positions coinciding This is roughly the current behavior. The issue is that it's unexpected that the animation would not be "ready" until the scroller becomes scrollable. E.g. when @kevers-google and @andruud were landing web tests they had to be very careful not to await the ready promise of a timeline on a zero range even though it feels like animations should eventually become ready even if the current state of the animation is inactive. From a developer point of view you could imagine a page sets up a parallax animation (and a bunch of other async tasks) and waits for all of the promises to resolve but on a large screen that animation never becomes ready preventing some other intialization logic from running. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9256#issuecomment-1714242894 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 11 September 2023 16:46:30 UTC