Thank you for your reply, Mike. The thing is that, even I press continue button of Firebug script debugging window when I encounter this, the page won't be loaded completely. Thereby, I cannot debug my codes.
For the example of http://blog.livedoor.jp/floweryday/archives/18417.html, if I DISABLE Firebug script debugging, then it will process 76 GET requests as you see at Firebug NET monitor panel window, and the page will be loaded completely. However, when I ENABLE Firebug script debugging and I press the continue button (couple times) to ignore this issue, then, as I wrote above, the page won't finish loading completely, I see about only 10 GET requests processed at the Firebug NET monitor panel window, and it stack there. So, I cannot work on my part with Firebug. Any suggestions? Regards On Jun 22, 7:45 pm, Mike Williams <nos...@econym.demon.co.uk> wrote: > It's not a problem, don't worry about it. > > The API references window.gtbExternal inside a try...catch clause and > takes the appropriate action when it catches the error. You only see > that error when you're actively debugging with a debugger that looks > inside try...catch. > > -- > 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 Google-Maps-API@googlegroups.com To unsubscribe from this group, send email to google-maps-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
