Skip to content

Navigator #16653

@alperozturk96

Description

@alperozturk96

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: FileDisplayActivityNavigatorActivityCommunityFragment
Second iteration: ActivitiesActivity

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions