Parallel route RSC does not unmount when navigating back to a `default.tsx` about next.js HOT 5 CLOSED

Hi, did you mean to share a different CodeSandbox? The one you shared is working fine for me.

from next.js.

I acidentaly fixed the sandbox with someone elses advice. The issue seems to be specific for default.tsx.
I've reverted the changes so the sandbox is working again.

from next.js.

I acidentaly fixed the sandbox with someone elses advice

How did you accidentally fix it? #50284 is full of ugly workarounds, so maybe your workaround works better than those until this is fixed...

from next.js.

Replacing the default.tsx with a page.tsx. It's not a 1 to 1 replacement, as it does not achieve the same functionality. But it fixed the issue on my specific use case.

from next.js.

Glad you got it working! It sounds like the behavior you were running into is expected behavior for default.tsx, described in a bit more detail here: https://nextjs.org/docs/app/api-reference/file-conventions/default

default.tsx is only used when the slot is first unmatched (ie, on page load). On soft navigations, whatever was in the slot will remain active, if it doesn't match to a page.tsx.

from next.js.