AFAIK this problem is directly connected with Firebug not being able
to show data without requesting it again. Hence, the double load. A
correct solution then should be that Firebug gets access to the
original data so that a second request is not ever needed. I'm not
familiar with Firefox internals so I don't know what the underlying
issue is but fiddling around with extra loads seems to be not the way
to fix it. A double GET request isn't really a problem requiring user
confirmation (unless the application is poorly designed and GETs are
having side effects), but a POST request should always have user
confirmation. Once the Firebug code can get the original data then
there is no need to resubmit in order to show the user the request
data. I await for the solution you mention from Firefox so that this
will work properly.
At least, this is my understanding of the issue and how it affects me.
I don't know what other issues people are having but I know this is
the one that causes me grief as it makes it very hard to debug POST
requests. The way I do that now is to have extra console.log calls
made in the response so that I can see the data returned without
clicking on the Firebug net tab to see the response data.
And in thanks to the Firebug team - I can only say that it makes one
realize that debugging modern ajax code without Firebug would be a
real hassle.
Chris :)
On Aug 25, 10:51 pm, John J Barton <
johnjbar...@johnjbarton.com>