On Sep 22, 1:34 pm, Anthony <[email protected]> wrote: > I'm just guessing here, but perhaps it has to do with whatever > function the API is using to grab the domain name (e.g. > window.location), and what it is returning. I would imagine that > browser implementations may not be consistent when dealing with > international domain names.
Indeed. There is also an issue with what browsers pass to Google to get a key, and how Google generates the key. For an internationalised domain name, there are potentially three points of failure (including the client when the map script is loaded). Unfortunately there is no easy fix. The best workaround is to host the map on a non-IDN domain, perhaps within an iframe in the IDN domain site. That way there is no problem with the key. You may want to add a star to Issue 12. http://code.google.com/p/gmaps-api-issues/issues/detail?id=12 Andrew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en -~----------~----~----~----~------~----~------~--~---
