That is an interesting thought. However, the Javascript documentation indicates that a try/catch block should catch errors before the window.onerror handler catches them. I would expect that google would use try/catch to catch errors rather than window.onerror. From my reading, an error that gets to the point that window.onerror is examined only has one more place to go, and that is the default error handler that normally pops up a message on the screen.
If you look at http://pond1.gladstonefamily.net/errorrate.png then you can see the sort of trending information that I collect. The big spike was when google switched to 2.140g. The end of the spike corresponds to when I changed my code to work better with whatever change they had made in the 2.140g version. It also appears that the transition from 180e to 184a roughly halved the number of errors that I am seeing. Philip On Dec 17, 12:17 am, Mike Williams <[email protected]> wrote: > If it is a Google lazy load effect, then Google should Catch and handle > the error. > > Is it possible that your reporting system records errors that have been > caught and successfully handled as well as "real" errors? > > -- > Mike Williamshttp://econym.org.uk/gmap -- 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.
