- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Sep 2022 16:12:02 +0000
- To: public-css-archive@w3.org
@ydaniv The input blocking referenced in #7797 is only for the duration when rendering is suppressed. Which starts one frame after createTransition (that is cached by the browser) and ends when the promise returned by updateDOM callback resolves. The duration while the animations run don't block input. Thanks for clarifying @birtles. The behaviour for the following states can then be: * `idle`: Ignored. If the animation is waiting to start at the next update the rendering loop it'll have a pending play task so will be considered `running`. * `paused`: Unclear whether this should be considered `active`. * `finished`: Ignored. If we're still waiting on dispatch of finish events we can rely on the pending animation event queue being empty. * `running`: Considered `active`. For the animation-timeline suggestion, it does make sense to exclude scroll-timeline but I'm not sure if we should exclude everything except document timeline. @flackr on this too. -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7785#issuecomment-1261139198 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 28 September 2022 16:12:04 UTC