Consider the following code:
hashString = window.location.hash.substring(1);
alert('Hash String = '+hashString);
When launched with the following hash:
#car = city% 20% 26% 20Country
the result in Chrome and Safari will be:
car = City% 20% 26% 20Country
but in Firefox (Mac and PC) it will be:
car = city and country
Since I use the same code to parse queries and hash parameters:
function parseParams(paramString) {
var params = {};
var e,
a = /\+/g,
r = /([^&;=]+)=?([^&;]*)/g,
d = function (s) { return decodeURIComponent(s.replace(a, " ")); },
q = paramString;
while (e = r.exec(q))
params[d(e[1])] = d(e[2]);
return params;
}
Firefox’s idiosyncrasy breaks it down here: “Vehicle parameter” becomes “city”, not a single country.
Is there a safe way to parse hash parameters in browsers or to fix how Firefox reads them?
.. Firefox HASH. :
queryString = window.location.search.substring(1);
alert('Query String = '+queryString);
:
= %20% 26 %20Country