NativeScript / NativeScript/angular
Wrong back navigation after using nested outlets with the TabsComponent
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 55
- Forks
- 13
- Avg merge
- 16m
- Merged PRs (30d)
- 1
Description
Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):
- CLI: 8.6.5
- Cross-platform modules:
- Android Runtime: 8.6.2
- iOS Runtime: -
- Plugin(s): -
- NativeScript-Angular: 16.0.1
- Angular: 16.2.0
Describe the bug
To Reproduce
I have created a demo app to reproduce the issue:
https://github.com/tujlaky/nativescript-tabs-demo
The following navigation steps would break the app:
- Item 1
- Show more
- Press the back arrow in the ActionBar twice
- Open the Browse tab
- Press Go outside button
- Press the back arrow in the ActionBar
- Open the Home tab
- It show Item 1
Expected behavior
It should how the last active view.
Sample project
https://github.com/tujlaky/nativescript-tabs-demo
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the reproduction app at github.com/tujlaky/nativescript-tabs-demo with the listed NativeScript, Angular, and Android Runtime versions. Follow the reported navigation sequence and inspect the TabsComponent and nested-outlet navigation behavior. Done means returning to the Home tab shows the last active view instead of Item 1.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100