You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Router.navigate doesnt work with relative route unless that route is currently active #38276
When using Router.navigate and passing a relative route in NavigationExtras, navigation silently fails unless the relative route is CURRENTLY active. Documentation does not state that relativeTo route must currently be active (though the class type is called ActivatedRoute), that restriction would seem to be unwanted, and in any event a silent failure to navigate is certainly not expected behavior.
Navigate to one by clicking the "one" button. This sets up a navigation function in NavigationService to perform navigation when called.
Click "Go to three using navigation service" button. The navigation function is called and app successfully navigates as expected.
Navigate to two by clicking the "two" button.
Click "Go to three using navigation service" button. The same navigation function that previously successfully navigated is called again but this time app silently fails to navigate.
Activity
angular-automatic-lock-bot commentedon Jun 24, 2022
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.