- From: kevers-google via GitHub <sysbot+gh@w3.org>
- Date: Fri, 29 Apr 2022 19:56:04 +0000
- To: public-css-archive@w3.org
kevers-google has just created a new issue for https://github.com/w3c/csswg-drafts: == [scroll-animations-1] Rethinking timeline-phase == At present, timelines have a before, active, and after phase, which can be confused with animation-effect phases. The before and after timeline-phases are exclusive to scroll-timelines. We could consider restricting the phases to active and inactive and simply allow timeline.currentTime to be outside the bounds of 0 to 100%. Doing so, may also alleviate some of the special casing that is performed when computing the phase of an animation-effect. A negative value for current time, regardless of units, would naturally result in the animation-effect phase being 'before' (assuming zero delay). Conversely, a value after effect end (100% for a progress-based animation) would result in an animation-effect's phase being 'after'. The special casing can be limited to what happens at the effect boundary, where it is conditionally exclusive with a time-based timeline and inclusive with a scroll-timeline. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7240 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 29 April 2022 19:56:06 UTC