That's really useful, because all the previous pages that have reported that problem have had huge quantities of other stuff going on at the same time, so it's been hard to tell what's really going on.
Starting with your code and throwing away everything that doesn't affect the problem produces a nice simple demonstrator that the Google guys can use to explore the problem. http://econym.org.uk/gmap/issues/issue737.htm One thing that's become apparent is that the problem only occurs in v2.129a onwards, so you can get round it by using &v=2.128d instead of &v=2 when you load the API code. I suggest that you add your star to issue 737 and 738, to encourage Google to mark one of them as "accepted" (and the other one as "duplicate"). -- http://econym.org.uk/gmap The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to Google-Maps-API@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
