Andrew Scott 9185c6e971 fix(router): ensure duplicate popstate/hashchange events are handled correctly (#37674) ...

The current method of handling duplicate navigations caused by 'hashchange' and 'popstate' events for the same url change does not correctly handle cancelled navigations. Because `scheduleNavigation` is called in a `setTimeout` in the location change subscription, the duplicate navigations are not flushed at the same time. This means that if the initial navigation hits a guard that schedules a new navigation, the navigation for the duplicate event will not compare to the correct transition (because we inserted another navigation between the duplicates). See https://github.com/angular/angular/issues/16710#issuecomment-646919529

Fixes #16710

PR Close #37674

2020-07-13 14:24:53 -07:00

..

aio-payloads.json

build(docs-infra): update @angular/material to 10.0.1 (#37898)

2020-07-08 16:02:46 -07:00

integration-payloads.json

fix(router): ensure duplicate popstate/hashchange events are handled correctly (#37674)

2020-07-13 14:24:53 -07:00