Repository navigation
Canceled Location.forward() breaks history #15664
Description
I'm submitting a ... (check one with "x")
[x] bug report => search github for a similar issue or PR before submitting
Current behavior
When CanDeactivate cancels Location.forward() routing history is 1 item ahead.
Workflow
Home -- navigate to --> Child 1
Child 1 -- navigate to --> Child 2
Child 2 -- navigate to --> Child 3 (CanDeactivate returned true)
Child 3 -- location.back() --> Child 2
Child 2 -- location.forward() --> Child 2 (navigation canceled CanDeactivate returned false)
Child 2 -- location.back() --> Child 2 (should be Route 1)
Expected behavior
Home -- navigate to --> Child 1
Child 1 -- navigate to --> Child 2
Child 2 -- navigate to --> Child 3 (CanDeactivate returned true)
Child 3 -- location.back() --> Child 2
Child 2 -- location.forward() --> Child 2 (navigation canceled CanDeactivate returned false)
Child 2 -- location.back() --> Child 1 (expected)
Minimal reproduction of the problem with instructions
http://plnkr.co/edit/PbKRj7v1B1tRVXRSrEup?p=preview
- Click button Child1
- Click button Child2
- Click button Child3
- Click button Back
- Click button Forward
- Click button Back
Expected behavior is to see Child1 but it's still Child2
Activity
patrickracicot commentedon Oct 25, 2017
Any progress on this issue? The PR #18135 for the referenced issue #18135 is still pending and the frequency seems to be bigger then initialy estimated.
atscott commentedon May 26, 2020
Confirmed and marking as duplicate of #13586. Example in #13586 (comment) extended to include this use-case.
angular-automatic-lock-bot commentedon Jun 27, 2020
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.