Post

If you thought we were done with View Transitions, guess again! A feature Chrome is working on, is “Scoped View Transitions”, which allow you to scope a VT to a subtree of the DOM. This unlocks things like concurrent transitions and prevents layering issues. developer.chrome.com/blog/scoped-...

26 reposts200 likes

Does that mean View Transition can be non blocking? I mean last time I checked while animating I couldn't interact with other elements on the page (such as buttons). If an element is in Scoped Transition can I click a button (separate element) for example and see it's effect?

With Scoped View Transitions, only the scope gets overlapped by the `::view-transition` pseudo. The same fix can be used to keep the scoped contents responsive to pointer events.

I’ve seen it work for <form method=get> as it counted as a navigation, but not for method=post. I have to add JavaScript that takes over the submit event and calls startTransition

In the video you can see how document-scoped and element-scoped transitions behave. When using the latter, the blue dot remains clipped by the scope; the popover remains visible on top of the scope; and the rest of the DOM remains interactive.