2

Google announced that after November 19th, a Maps v2 to v3 wrapper would be deployed:

On November 19, 2013 we will deploy a JavaScript wrapper that attempts to automagically turn remaining v2 maps into v3 maps. Though we expect this wrapper to work for most simple maps, we cannot guarantee that your maps will continue to function. We therefore highly recommend that you migrate to v3 before November 19. The good news is that Google Maps JavaScript API v3 is more robust and feature rich than v2, and we’ve written a guide to assist the migration.

This seems to work with simple maps in Chrome 31, however it fails with IE9 or Firefox 25.

Has anybody managed to get the wrapper to work in another Browser than Chrome?

UPDATE: Ok, the wrapper seems to work now for Chrome, Safari, FF and IE.

sladstaetter
  • 453
  • 4
  • 11
  • 1
    Is there a code question? If it doesn't work for you, migrate to the v3 API. – geocodezip Nov 20 '13 at 15:28
  • Ok, seems it's a temporary issue - FF at least works with the sample site now. – sladstaetter Nov 20 '13 at 17:08
  • Neither Chrome nor FF works: http://artax.karlin.mff.cuni.cz/~ttel5535/pok_gm/g_simplest.html – Tomas Nov 20 '13 at 18:29
  • 1
    geocodezip, your comment is annoying and not constructive at all. This is real problem all v2 applications are now facing. – Tomas Nov 20 '13 at 18:32
  • @Tomas Your sample works for me if the language parameter is removed at the end of the api inclusion path: "&hl=cs" – sladstaetter Nov 20 '13 at 19:17
  • Everything works *now*! It seems that Google has been debugging the wrapper script in the meantime. Do you still see any problems anywhere? – Tomas Nov 21 '13 at 17:46
  • @Tomas the only (minor) issue I encountered is that InfoWindows aren't positioned correctly if custom markers are used. In fact most examples from https://google-developers.appspot.com/maps/documentation/javascript/v2/examples/ seem to work. – sladstaetter Nov 21 '13 at 19:04

0 Answers0