Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(angular): nav controller can pop views after leaving tabs outlet #25690

Merged
merged 15 commits into from
Sep 8, 2022

Conversation

sean-perkins
Copy link
Contributor

@sean-perkins sean-perkins commented Jul 28, 2022

Pull request checklist

Please check if your PR fulfills the following requirements:

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been reviewed and added / updated if needed (for bug fixes / features)
    • Some docs updates need to be made in the ionic-docs repo, in a separate PR. See the contributing guide for details.
  • Build (npm run build) was run locally and any changes were pushed
  • Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

  • Bugfix
  • Feature
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes
  • Other (please describe):

What is the current behavior?

The Angular routing implementation had a race condition when re-entering a tabs outlet. The router outlet would be activated with both the application root ion-router-outlet as well as the tab's router outlet.

Setting the active view waits for the entering view to finish transitioning. Due to how we deterministically set the top outlet, this would always cause the root router outlet being assigned as the top outlet, even though the tabs router outlet was technically the top outlet.

This results in the navController.pop() attempting to pop a view from the top outlet (the root outlet), which does not have views in the stack to remove.

Issue URL: #18593

What is the new behavior?

  • The top outlet is set synchronously, to avoid a race condition of the top outlet being set incorrectly (when dealing with nested outlets).

Does this introduce a breaking change?

  • Yes
  • No

Other information

Dev-build: 6.2.5-dev.11661886076.141059a8

@github-actions github-actions bot added the package: angular @ionic/angular package label Jul 28, 2022
@sean-perkins sean-perkins marked this pull request as ready for review July 28, 2022 20:53
@sean-perkins sean-perkins requested a review from a team as a code owner July 28, 2022 20:53
@sean-perkins sean-perkins removed the request for review from a team July 28, 2022 21:58
@sean-perkins
Copy link
Contributor Author

Ok @liamdebeasi @amandaejohnston this is ready for review. I'm creating a new dev-build, but based on the age of the issue I do not believe we will get testers. We have added test cases to account for expected behavior in the test apps.

@sean-perkins sean-perkins merged commit 725b13f into main Sep 8, 2022
@sean-perkins sean-perkins deleted the fix/angular-nav-controller branch September 8, 2022 16:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
package: angular @ionic/angular package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants