When navigating to a modal, then following a route that also presents as a modal, the following occurs:
First modal navigation works as expected
Second modal navigation works as expected (unsure if first modal is expected to remain 'behind' this one, it does)
Closing second modal results in the first modal being revealed, but no interaction works, except for closing the modal.
The logs indicate the visit location upon closing the second modal (signup route) becomes the root route, not the login route.
Expectations:
If we expect the original (first) modal to remain, then closing the second modal should render the original modal interactable
If we don't expect the original (first) modal to remain, then visiting another modal should dismiss the original modal, or treat it as a "replace" action.
Through testing, this only occurs when the modals use uri: "turbo://fragment/web/modal/sheet" which uses a TurboWebBottomSheetDialogFragment(). If all path configs use "turbo://fragment/web" it seems fine.
Let me know if I have configured something incorrectly. For context my path configuration has:
When navigating to a modal, then following a route that also presents as a modal, the following occurs:
The logs indicate the visit location upon closing the second modal (signup route) becomes the root route, not the login route.
Expectations:
Through testing, this only occurs when the modals use uri:
"turbo://fragment/web/modal/sheet"
which uses aTurboWebBottomSheetDialogFragment()
. If all path configs use"turbo://fragment/web"
it seems fine.Let me know if I have configured something incorrectly. For context my path configuration has:
Video
Screen_recording_20240615_112959.webm
Logcat