When the user lifts their finger and the gesture is committed, the gesture-timeline will progress to 100%. But the user still has the option to cancel the navigation by using the stop option in browser UI.
It seems like we should keep the entire ViewTransition state alive on the current Document until there is a network response for the navigation and its not cancellable. If the user does hit stop before this point, we can play the timeline in reverse and dispatch an event indicating the navigation was aborted. Since authors would already expect the reverse navigation for the gesture abort case, the UI would look the same.
When the user lifts their finger and the gesture is committed, the gesture-timeline will progress to 100%. But the user still has the option to cancel the navigation by using the stop option in browser UI.
It seems like we should keep the entire ViewTransition state alive on the current Document until there is a network response for the navigation and its not cancellable. If the user does hit stop before this point, we can play the timeline in reverse and dispatch an event indicating the navigation was aborted. Since authors would already expect the reverse navigation for the gesture abort case, the UI would look the same.