I don't use lazy loading, but I know that Google Maps does. Is this problem related to that -- I don't know.
*I* have never seen this problem -- and I try my app in four different browsers on different OSes. Someone asked why I generate these logs -- it allows me to monitor my application when it actually runs. In particular, when google releases a new version of the API code, I can sometimes see a dramatic change in the number of errors reported. I also report a hit for each error to google analytics that includes the maps version number. This is really quite revealing. To those of you out there who still question why I track errors -- I have a question for you: Why *don't* you track errors in your app? If you think that every error will be reported to you, then you will be surprised if you add tracking. Philip On Dec 16, 8:38 pm, Rossko <[email protected]> wrote: > > 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.
