- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 May 2023 13:56:21 +0000
- To: public-css-archive@w3.org
> You would see the attached timeline as of the _previous frame_ Can you explain this? If the timeline attachment changes it changes for the current frame doesn't it? Otherwise you could have a flash of content at a completely different position. The previous frame current time in the spec is meant for cases where the source isn't changing so that we don't have to flush style and layout again if the scroll position changes after or as a result of animating. > which for newly created animations means `getAnimations()[i].timeline` would return no timeline. `getAnimations()` forces a style and layout to ensure it picks up newly created animations. Wouldn't this pick up the currently resolved timeline? > A simple solution is to just use two `-root` properties. It's putting a bit of extra awkwardness on developers to have two root properties gathering names for the same conceptual `animation-timeline` namespace which could hypothetically include future named timeline types as well. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7759#issuecomment-1533075700 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 3 May 2023 13:56:23 UTC