Angular.js $location.path(url) loop back to root in windows mobile IE

[thinknikhil]

We are using the angular js in the mobile development. It works fine in iOS and Android mobile browser.

We have few routes in the application and use $location.path(href) to change the route. All works fine in iOS and Android mobile devices.

In windows mobile IE when we change 2 to 3 routes and tries to hit the device back button it directly takes me back to the root instead of taking to one step back in the window.history.

If we use the $window.location.hash to change the location then the history issue goes away but then there is a [$rootScope:infdlg] 10 $digest() iterations reached. Aborting watchers fired in the last 5 iterations issue is seen.

Is there any workaround to get around the issue?

[caitp]

I'm not equipped to deal with debugging/fixing IE mobile issues, but I encourage you to find the issue in angular, and write a patch to correct it. It most likely won't take too much of your time.

[thinknikhil]

The workaround is to use location.href instead of history.pushState(null, '', url); on line 4221 of angular.js v 1.2.10 then it fix the issue.

The problem In IE mobile is $sniffer.history is true because it has the history pushState feature but when the url pushed with hashBang it behaves weirdly and doesn't maintain the stack.

In angular even after setting the html5Mode to false the $sniffer.history value is true and then it tries to use the history.pushState feature. Angular should not use history pushState on setting the html5Mode to false.

[mgibas]

Can confirm this bug on WP 8 and WP 8.1

[carlhopf]

can confirm this issue still exists with angularjs 1.3-beta13, WP 8.1

[btford]

@thinknikhil @mgibas @mrlocus would any of you like to write a patch to fix this?

[ScooterOk]

Will this fixed a bug in the near future ?

[fobin]

I fixed this in 1.2.21 like this since I need my app to work only mobile platforms:
Line 4479:
if ($sniffer.history) {
Replace with:
if ($sniffer.history && ! $sniffer.msie) {

[caitp]

Will this fixed a bug in the near future ?

It will be fixed when we get a CL that fixes it in a good way =)

[rbhargaw]

Thanks Fobin, that line of code fixed the issue!

[Nash171]

Is this issue still exists?