Dismissing a TurboNavPresentationContext.MODAL visit by performing a DEFAULT context visit breaks the app when there's more than 1 MODAL context visit in the backstack.
The app doesn't properly replace the underlying /tasks fragment. What seems to happen instead is that it tries to go back to /tasks/wizard/step-1 and breaks.
Unfortunately, this means that if you're in a multi-step form, and you remember something you needed to change in the previous form, you'll then have to close the entire form and start again.
Looking into the navigation code, I noticed that the behaviour achieved with subsequent wizard steps performing a replace is totally independent of presentation context, as per TurboNavRule:64
Dismissing a
TurboNavPresentationContext.MODAL
visit by performing aDEFAULT
context visit breaks the app when there's more than 1MODAL
context visit in the backstack.Suppose we have this configuration.json:
This sequence of visits works as expected:
However, if we have this sequence of visits...
The app doesn't properly replace the underlying
/tasks
fragment. What seems to happen instead is that it tries to go back to/tasks/wizard/step-1
and breaks.Here's a video for demonstration:
https://user-images.githubusercontent.com/25386350/156970441-ed353ecf-9d9c-4126-a847-aeadb48d31dc.mov
That can be 'fixed' it by adding this rule:
Unfortunately, this means that if you're in a multi-step form, and you remember something you needed to change in the previous form, you'll then have to close the entire form and start again.