Apostrophe in Querystring Value in Firefox breaks angular #920

nickretallack opened this Issue May 1, 2012 · 5 comments


None yet

2 participants



This is a serious bug that causes angular to stop functioning until you refresh the page. This happens any time there is an <ng-view> on the page and an apostrophe in a querystring argument. It happens in Firefox, but it does not happen in Chrome. I'm using Angular 1.0rc6. The error message it produces is below.

10 $digest() iterations reached. Aborting!
Watchers fired in the last 5 iterations: [["fn: $locationWatch; newVal: 7; oldVal: 6"],["fn: $locationWatch; newVal: 8; oldVal: 7"],["fn: $locationWatch; newVal: 9; oldVal: 8"],["fn: $locationWatch; newVal: 10; oldVal: 9"],["fn: $locationWatch; newVal: 11; oldVal: 10"]]

Source code for the example program:

<!doctype html>
<html ng-app>
    <script src="http://code.angularjs.org/angular-1.0.0rc6.js"></script>

Btw, this is curiously similar to this bug: #904


Here's the problem. We're comparing location.href to a location constructed from its components. Unfortunately in Firefox the hash part of location.href is not the same as location.hash when any special characters are used. location.href is fully escape()'d, while location.hash is unescape()'d. If you have an apostrophe in your url, angular compares and assigns these values repeatedly and they never become equal.


In Chorme, location.href does not escape apostrophes.


Okay, it appears apostrophes are the only thing causing the inconsistency. Firefox escapes them and Chrome does not. escape() escapes them and encodeURIComponent and encodeURI do not. To patch up the inconsistency, modify Browser#url like so:

<       return location.href;
>       return location.href.replace(/%27/g,"'")

I've filed a bug on firefox.

@IgorMinar IgorMinar was assigned May 7, 2012

I'll look into this week. Thanks for the detailed info.

@IgorMinar IgorMinar added a commit that closed this issue May 14, 2012
@IgorMinar IgorMinar fix($browser/$location): single quote in url causes infinite digest i…
…n FF

The real issue is in FF, see https://bugzilla.mozilla.org/show_bug.cgi?id=407172.

FF overly encodes stuff which breaks our expectations and then we fail .url() != currentUrl.absUrl()
comparison unexpectidly, which leads to infinite digest.

The workaround is to correct for this inconsistency in $browser and decode any single quotes in urls.

Closes #920
@IgorMinar IgorMinar closed this in 679cb8a May 14, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment