$location + html5 mode + legacy browser + #url('/newUrl') => full page reload

[IgorMinar]

it seems that we do something wrong when $location is in html5 mode and we run in a browser that doesn't support history.pushState and we change url with $location#url() method.

angular.module('myApp', [])
    .config(function($locationProvider){
        $locationProvider.html5Mode(true).hashPrefix('!');
    }
);

function MyCtrl($scope, $location) {
   $scope.changeURL = function() {
        $location.path('/myPath');
  }
}

<a href ng-click="changeURL()">click here to see full page reload</a>

originally reported at: https://groups.google.com/forum/?fromgroups#!topic/angular/k-i6UYa7KpQ

[bonya]

I experience similar problem in a Chrome (22.0.1216.0 canary) with html5mode=false;

The url schema is:

...
.when('/users', {templateUrl: 'partials/list.html', controller: UserListCtrl})
.when('/users/:userId', {templateUrl: 'partials/user-detail.html', controller: UserDetailCtrl})
...

When i use ng-click to return from /users/userId to /users with location.path('/users'), browser first correctly goes to #/users, displays the expected partial, an just in a moment reloads the page with ?#/users url.

Navigation to /users from /users/userId with a simple anchor href="#/users" works fine.

[stereosteve]

I am having a similar issue. When hitting a "deep link" on IE, angular will redirect to the hashbang version, but it will throw errors in the IE console that 10 $digest() iterations have been reached - I asked about this on the mailing list

I also experience this when visiting the angular api documentation on IE

[cfchase]

EDIT: Since my problem isn't legacy browser related and is currently breaking all my ng-click anchors, I'll post on google groups and maybe submit a separate ticket.

----------------- Original Post Follows ----------------------

This is a similar issue to the problem I'm having, so I thought I'd comment here. If not appropriate, I can file separately. It's happening for me on Chrome dev (22) and FF14, so for me it's not a legacy browser problem in my case.

I have a problem where a blank href in an anchor performs the ng-click function and is still redirecting me to the base href of my app.

 <a href="" ng-click="myFunction()">link 1</a>

I'm using html5Mode and have a <base href="/app/">

Perhaps I'm routing incorrectly or there's a better way.

Here's a link to reproducing the problem against angular-seed. https://github.com/cfchase/angular-basehref-anchor

[farin]

I am observing same issue as bonya. It happens only in Chrome (my version is 20) and also happens also in html5mode = true

/somepath is redirected to /somepath? causing page load

[RichJohnson2]

This could be related to issue #1090 which is a cookie issue that stems from the "baseHref" function returning undefined on some browsers. This function is called from 2 places in Angular:

• cookiePath in the ng.$browser#cookies function
• basePath in the ng.$locationProvider#html5Mode function

This failure may depend on whether the you're using jQuery or the Angular jQuery-lite library.

[farin]

more observation:

• I am using regular jQuery
• when I wrapped $location.path call in 1ms $timeout, it work fine also in chrome

[bartkowiakmateusz]

I've got the same issue. It seems that the problem occurs only after going back to route, that has been previously visited. Chrome 21, html5 = false.

[ajaybeniwal]

angular.module('phonecat', []).
config(function ($routeProvider, $locationProvider) {
// $locationProvider.html5Mode(true);
// $locationProvider.html5Mode(true);
$routeProvider.
when('/phones', { templateUrl: 'AngularMVC/partials/phone-list.html', controller: PhoneListCtrl }).
when('/phones/:phoneId', { templateUrl: 'AngularMVC/partials/phone-detail.html', controller: PhoneDetailCtrl }).
otherwise({ redirectTo: '/phones' });
// $locationProvider.html5Mode(true).hashPrefix('!');
$locationProvider.hashPrefix('!')
$locationProvider.html5Mode(true);

});

But when i click on phone templateURL field is not set properly any idea

[nicola]

isnt that fixed yet?

[scottweinert]

Is this fixed? I seem to be having this problem.

[just-boris]

wrapping $timeout did the trick, but IE works in hashbang mode and this hack doesn't help

[dfbaskin]

I am seeing this same issue when using IE9. Posted to AngularJS group here:
https://groups.google.com/forum/?fromgroups=#!topic/angular/_iP4sGnLmqo

The associated Plunker:
http://plnkr.co/edit/44B5KBOGqUFqa2kvAjMM

[gamebox]

I see that this issue is still open, is this at least fixed farther along the 1.0.x branch? Or farther along 1.x? This is causing serious headaches.