See my test page.
When on the page, click the top left button “Geocode”. If you are in Firefox, geocoder.geocode() will have it’s status equal to ERROR (and pop an alert after a few seconds). In Internet Explorer (at least 7), everything is fine and the marker is added to the map.
If you remove the quote from the address (l’Assomption –> lAssomption), everything execute fine in Firefox.
Now with my question: how a quote can “crash” the Google Maps V3 API only in Firefox!?
UPDATE: Status of my report has beed changed to “Confirmed” by Google. It seems it’s really a V3 bug. While it’s fixed, I remove quotes from the address before geocoding (Google Maps is smart enough to find it without it).
That’s weird. When I try it in Firefox the response code from the server is 403. Here’s test link to the API call as reported in Firebug
5415 boul. de l’Assomption, Montreal, Quebec, H1T2M4, Canada
So, then I loaded it up in IE and fired up Charles. Here’s the link to the API call generated by IE.
5415 boul. de l’Assomption, Montreal, Quebec, H1T2M4, Canada
See the difference? Firefox is encoding the
'into%27whereas IE is not.Conclusions
403 - Forbiddenas a false negative.Long story short? Seems like a bug.