> In the past, I've seen other maps related JS errors and they turned > out to be related to the maps lazy loading of scripts and they are > subtle timing issues.
Well, who knows? The logs are pretty useless for guessing at things like that, since there's absolutely no clue as to whether you use lazy loading at all, let alone if that is where the problem lies. As already said, if the errors are client-side, you really need to look at the client-side code running on a client. If you suspect a timing problem, you could try your page in various browsers on both a fast client with broadband, and a elderly laptop on dialup ; it might just show something up. If you haven't got access to that sort of thing, people round here might; but at the moment they have no way to help you. -- 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.
