Scoped view transitions
I couldn't find any threads discussing this, so I wanted to ask what (if any) are the plans with scoped view transitions:
https://developer.chrome.com/blog/scoped-view-transitions-feedback
I've recently migrated my personal application from motion -> view transitions, and the immediate problem I have is that view transitions block the entire page - making navigation or cancellation of a transition impossible. Scoped view transitions should solve this by allowing the browser to only animate a particular sub tree of the browser.
In my opinion, the router is a fantastic place for this, because each outlet effectively acts as a transition boundary. This would mean that when changing routes, that retain a shared parent route, only that sub-document needs to be transitioned, rather than the entire page - keeping navigation responsive, and providing better cross page transitions.
With all this in mind, It's currently behind a flag in chrome 140, so it's still early days, but I'm curious if any thought has been given to what that API would look like from the router perspective? There could likely be very little work, and it simply automatically behaves as I described above, but I'm sure there are edge cases or considerations for supporting that.
https://developer.chrome.com/blog/scoped-view-transitions-feedback
I've recently migrated my personal application from motion -> view transitions, and the immediate problem I have is that view transitions block the entire page - making navigation or cancellation of a transition impossible. Scoped view transitions should solve this by allowing the browser to only animate a particular sub tree of the browser.
In my opinion, the router is a fantastic place for this, because each outlet effectively acts as a transition boundary. This would mean that when changing routes, that retain a shared parent route, only that sub-document needs to be transitioned, rather than the entire page - keeping navigation responsive, and providing better cross page transitions.
With all this in mind, It's currently behind a flag in chrome 140, so it's still early days, but I'm curious if any thought has been given to what that API would look like from the router perspective? There could likely be very little work, and it simply automatically behaves as I described above, but I'm sure there are edge cases or considerations for supporting that.
Chrome for Developers
Help us build the next iteration of View Transitions
