Thanks for the fix, but surely if/when google fix it you will have a problem because the function has already been defined. In which case Zanardi's fix is safer as it is a variable rather than a function, thus the real one can safely override it (I may be wrong).
Loading from a clean cache seems to be returning API versions with and without the bug - presumably because of propagation through a CDN. So hopefully our maps will be back up soon... Cheers, Alistair http://www.zoombu.co.uk On Aug 17, 11:25 am, "Klaus, GPSies.com" <[email protected]> wrote: > Hi, > > I do have a workaround (just implementing the function), which is > working fine for me. > > <script type="text/javascript"> > function tick(what) { > // console.log(what); > } > </script> > > <script type="text/javascript" > src="http://maps.google.com/maps? > file=api&v=2&key=..."></script> > > I'll let it inside the code, until Google fixed it. > > Regards, Klaus (http://www.gpsies.com/) -- 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.
