On Aug 5, 12:16 am, alee <alee94...@gmail.com> wrote: > > I am also running Firebug 1.3.3. While this is happening, if one > clicks X in the browser and performs a refresh, the page then loads. > > Disabling Firebug 1.3.3 on the same pages does not yield the problem. > > Any possibilities of resolution from GoogleMaps point of view?
I doubt it; I reckon this is a problem with Firebug. 200-series status codes are "success" codes, and "204 No content" is simply a report that there is nothing to report, as it were. It shouldn't trigger Firebug. It has been noted in the group that trialling a beta version Firebug 1.3.4 indicates it may be ok -- or it may be back to normal when it's released, of course. I suppose there is the possibility that Google could change the 204 code to "200 OK" which should fix the problem; but presumably there's a reason why they used 204 in the first place. Andrew --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
