router.push not working properly in intercepting modal routes. about next.js HOT 2 CLOSED

Hi @stayclaxxy! This looks to be expected behavior during soft-navigations of parallel routes. You can read a bit more about how that works in this section of the parallel routes docs. Specifically:

Soft Navigation: During client-side navigation, Next.js will perform a partial render, changing the subpage within the slot, while maintaining the other slot's active subpages, even if they don't match the current URL.

What's happening in your reproduction is that when you arrive on the /test page, the @modal slot is matched to default.tsx. Then when you trigger the interception, the @modal slot is matched to @modal/(.)broken/page.tsx. Now when you click the close button in your modal, this triggers a soft navigation back to /test. It's going to try and find a parallel route at @modal/page.tsx. A slot will never go from showing page -> default (only the reverse is possible). Since it can't find that component, it keeps what was active there before, which in this case was your modal. So your modal component is technically still mounted, but just hidden, because you called setOpen(false).

To fix this in your reproduction, you just need to create a @modal/page.tsx that returns null. Here's your CodeSandbox forked, with that change: https://codesandbox.io/p/devbox/parallel-routes-weird-behavior-forked-kdxmvj

Along with a quick demonstration:

from next.js.

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

from next.js.