fix(react-router): allow swipe back over a splat container page

[ShaneK]

Issue number: resolves #31479

---

What is the current behavior?

Currently, swipe-to-go-back does nothing over a splat container page in the root outlet. canStart decides whether the entering and leaving views are the same by comparing the entering view's resolved pathname against the current pathname, and a splat consumes whatever is left of the pathname, so its match always resolves to the whole current pathname. At the root that is every pathname, so the gesture is rejected before it starts.

What is the new behavior?

We now compare the view items directly, the same way onEnd a few lines below already does, so a container page sitting underneath a pushed sibling is no longer mistaken for the page being left. canStart also requires a leaving view now, because without one onStart reveals the entering page but never builds a progress animation, and core only calls onEnd when an animation exists, so the reveal was never undone and goBack never fired.

The pattern.path !== routeInfo.pathname condition came out with it. pattern.path is the declared route path, so it is either a wildcard or param pattern that can never equal a pathname, or a static path where the view comparison already rejects the gesture.

Does this introduce a breaking change?

• Yes
• No

Other information

Stacked on #31481, which fixes the same issue for a splat one level down. This is the root outlet case, which that PR left open.

The reproduction needs its own React root. A root catch-all can't live in the shared route tree in App.tsx without swallowing every other spec's pathname, so the test index.tsx picks between App and RootSplatSiblingApp by pathname.

All five new tests fail on main and on #31481's branch alone, proving they cover the gap here.

Root splat sibling test page

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
ionic-framework	Ready	Preview	Sep 25, 2026 3:14pm UTC