Are modal screens (dialogs or bottom sheet from accompanist) expected to not stay in the back stack ...

# compose

[Rafael Costa]

Are modal screens (dialogs or bottom sheet from accompanist) expected to not stay in the back stack after navigating away from them?
I've had issues opened on my library about this and I'm not sure if this is expected. At the moment they are not kept unless we navigate to another modal screen. So is this intended or should I open an issue?

[myanmarking]

I dont know :p i have never needed a persistent bottom sheet, but i would say, as the name implies, should appear on back if previously opened. I am only using modal bottom sheet, and they go away if you navigate to another screen. Also, i am not persisting them (which is debatable). So for instance on process death it wont appear. Which is fine in my cases. Confirmation dialogs the same for me. I dont know if there are guidelines for this

[Rafael Costa]

Found an answer for non compose navigation

[Rafael Costa]

From @Ian Lake . I'm guessing this is expected here for the same reasons

[Rafael Costa]

https://stackoverflow.com/questions/67237079/how-to-prevent-bottomsheetdialogfragment-from-dismissing-after-a-navigation-to-a

[Ian Lake]

Yep, WAI as per the docs on FloatingWindow destinations (which would include dialogs, bottom sheets, etc): https://developer.android.com/guide/navigation/navigation-navigate#back-stack

[Ian Lake]

Something we just talked about last week also: https://kotlinlang.slack.com/archives/CJLTWPH7S/p1647869845463179?thread_ts=1647816927.842829&cid=CJLTWPH7S

[Rafael Costa]

Great, thank you for confirming 🙏