Khushal Sagar

**Proposed Resolution**: User input is discarded for each Document with [transition suppress rendering](https://drafts.csswg.org/css-view-transitions-1/#document-transition-suppressing-rendering) set.

I have a mild preference for `createDocumentTransition(callback, initDictionary)`. The non-optional parameter followed by an optional dictionary. This matches the `element.animate(keyframes, options)` syntax too.

Discussed this offline today and the conclusion was that createDocumentTransition(callback) is the simpler and preferable syntax. So **proposed resolution**: "createDocumentTransition takes a callback". @jakearchibald if I'm reading the whatwg issue...

The downside of making it async is the following sequence: - Queue a transition with createDocumentTransition. - While snapshot is pending (so the callback hasn't run) initiate a new transition...

Summary from offline discussion. Microtasks need a checkpoint to ensure they run before a specific event. Since there is already a checkpoint for [Web Animations](https://drafts.csswg.org/web-animations-1/#update-animations-and-send-events:~:text=Perform%20a%20microtask%20checkpoint), using a microtask will ensure...

The proposal is to use a [task](https://html.spec.whatwg.org/multipage/webappapis.html#concept-task) instead of microtask. Microtask timing can be unpredictable since the microtask checkpoint which runs them can be triggered by any feature.

I think we can defer this until we see use-cases hitting this in practice. The whole point of the updateDOM callback is to allow the developer to fetch all resource...

Summary from offline discussion: It makes sense to abort the transition if per element constraints are broken, i.e., no layout containment or the element allows fragmentation. But detecting if the...

We had an offline discussion about this, summarized below. There are 2 different points to resolve for this issue: 1. If an element is participating in a transition, any element...

`getBoundingClientRect` is fine for the element with `content-visibility: auto` since that element has been styled/laid out. But if you call it for one of its descendants, it forces a style/layout...