-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Open
Labels
enhancementnavigationNavigation matters (e.g. covered under #11072)Navigation matters (e.g. covered under #11072)technical debt
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Currently, navigation between screens launches separate activities, each managing their own fragment stack. This leads to coupled, inconsistent back stack behavior across the app.
Migration path
Each screen is a Fragment hosted inside NavigatorActivity and eventually FileDisplayActivity owns the single FragmentContainerView and Navigator instance. All navigation flows through FDA, giving the app a unified fragment back stack.
First iteration: FileDisplayActivity → NavigatorActivity → CommunityFragment
Second iteration: ActivitiesActivity
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementnavigationNavigation matters (e.g. covered under #11072)Navigation matters (e.g. covered under #11072)technical debt