Khushal Sagar

Summary from offline discussion: Makes sense to follow the WA-API model and have the document.createDocumentTransition API also start the transition by initiating the capture phase. Registering a callback on a...

Always having isolation/mix-blend-mode can be a footgun since any content generated by these 2 nodes (like the developer adding `background` to the wrapper) will force us off the fast path.

> I think it's ok for the transition to be infinite if the developer has deliberately paused the animation. +1. I assumed that the developer may also pause the animation...

@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...

I'm not sure how gesture based transitions can be built using scroll timeline yet. The swipe gesture imitated by the user would be a trigger to initiate the transition itself....

> which is later only progressed if the user continues scrolling on same direction. These types of transitions are generally set up to commit to either the new or current...

Concluding the discussion so far. The transition reaches a state with no active animations when the following is true: 1. None of the transition pseudo-elements have an animation in [paused](https://w3c.github.io/csswg-drafts/web-animations-1/#paused-play-state)...

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...

Thanks for that example! Agreed on including all Document timelines associated with the Document but excluding monotonically increasing timelines. I've sent you a PR [here](https://github.com/w3c/csswg-drafts/pull/7857) to make sure the spec...

> "execlude non monotonically increasing timelines", right? Sorry I meant to say "Agreed on excluding all timelines other than Document timelines". > The main difference I guess is that these...