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 }}
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
This can lead to unresponsive pages as the browser attempts to make N number of requests during page load where N is the number of digests that occur after setting up $location.
Note that this is also occurring on angularjs.org. It's just less severe because there are few digests that occur after page load. As such, it maybe related to #6820 .
Reproducible: always Browsers: IE9 (Most probably affects IE7 and IE8 too, but I haven't tested it) Affects: Regression from AngularJS 1.2.24 and 1.3.0-RC.0
This is caused by 2ece4d0 (#6976), since fireUrlChange sets newLocation to null (on this line) and it doesn't account for the fact that setting href is async on IE9.
As setting location.href isn't synchronous on IE9, each digest cycle is actually clearing the locationUrl state (that's used to save the navigating state for IE9) so the digest initiates another change to location.href on every digest and the browser actually sends another request instead of continuing to navigate to the same href set previously (in the previous digest cycle).