Re: [csswg-drafts] [css-shared-element-transitions-1] Define "active animation" used to signal end of transition (#7785)

Thanks for the question @birtles. Can you give an example of a document timeline (other than the default document timeline) which is associated with the a document. I couldn't figure out how these would be created/used from the spec text regarding [timelines associated with a document](https://drafts.csswg.org/web-animations-1/#timeline-associated-with-a-document).

I want to avoid including timelines which are not guaranteed to move forward at frame boundaries. They could rely on events which may not occur and that makes it unclear how the animation will finish. That's not the issue with the default document timeline based on the text [here](https://drafts.csswg.org/web-animations-1/#document-timelines:~:text=since%20the%20time%20values%20of%20the%20default%20document%20timeline%20have%20a%20zero%20offset%20from%20the%20time%20origin%2C%20document.timeline.currentTime%20will%20roughly%20correspond%20to%20Performance.now()%20%5BHR%2DTIME%5D): "since the [time values](https://drafts.csswg.org/web-animations-1/#time-value) of the [default document timeline](https://drafts.csswg.org/web-animations-1/#default-document-timeline) have a zero offset from the [time origin](https://w3c.github.io/hr-time/#time-origin), document.timeline.currentTime will roughly correspond to [Performance.now()](https://www.w3.org/TR/hr-time/#dom-performance-now) [[HR-TIME]](https://drafts.csswg.org/web-animations-1/#biblio-hr-time)".

But I'm not sure if the above is true for other document timelines or the generic monotonically increasing timelines. While its clear that these timelines will always move forward, I'm not sure what triggers their advancement.

-- 
GitHub Notification of comment by khushalsagar
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7785#issuecomment-1270500477 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 6 October 2022 18:20:16 UTC