Net Panel And Ajax Responses
53 views
Skip to first unread message
Sam
Aug 9, 2011, 2:30:38 PM8/9/11
to fir...@googlegroups.com
Hey folks!
Guys, terrific work with this tool, i really appreciate all the efforts given to this and specially to the attention to users, Man! you must be close to Gandhi when it comes to patience to deal with all of us.
So, after several months without a single slip from firebug to me, i've come to a vicious bug (if it is) that has given me quite some gotchas lately, you see... here at work we are creating a reporting tool for our customers, and this page has a massive amount of ajax.
Net Panel is fundamental for us to catch the requests and responses and all that magical things that happens in between, but sometimes (not always) the net panel keeps showing the "loading" status on a request that has been completed and already on the page.
Let me explain a little further.
When we click on a button to display a grid, we send a request to the server with jQuery's $.ajax and on the server we query the DB, perform some stuff and then convert the data from the DB to a json object, then we respond that object to the client and BAM! done.
All this is donde superb and the Net Panel catches all this requests/responds and shows the time, the amount of data (KB / MB), parameters etc etc.
But sometimes, all of this is performed, the data is already displayed on the page but on the Net Panel the loading image is still spinning and never stops, if i go and debug the js of the jQuery's $.ajax => success: function, i hit the breakpoints and all of that, but the .Net Panel is still spinning.
I've tried to catch the culprit, whether it's a bad json / xml, a timeout ( unlikely because the most heavy transaction is merely 4 seconds ), you name it. And the funny thing is it doesn't shows up in the same request. For example, i have Button A and Button B, i press B-A and Net Panel spins and stops, press B-B Net Panel Spins and stops, play a little with those buttons and BAM, a never ending spinning is there, GOTCHAS: i don't push the buttons until a response has finished ( Data is displayed on the page ) so don't think i'm mashing the buttons non-stop.
Anyway, it's no biggie, just something that is a little annoying because it seems to know when i want to get the time of the request to spin until eternity.
Oh and another thing, on the Console Panel it always spins and stops no matter what, so, i've been using that panel lately, but i am constantly clearing it because it grows like there's no tomorrow with all the js debbuging and stuff.
Thanks!
Guys, terrific work with this tool, i really appreciate all the efforts given to this and specially to the attention to users, Man! you must be close to Gandhi when it comes to patience to deal with all of us.
So, after several months without a single slip from firebug to me, i've come to a vicious bug (if it is) that has given me quite some gotchas lately, you see... here at work we are creating a reporting tool for our customers, and this page has a massive amount of ajax.
Net Panel is fundamental for us to catch the requests and responses and all that magical things that happens in between, but sometimes (not always) the net panel keeps showing the "loading" status on a request that has been completed and already on the page.
Let me explain a little further.
When we click on a button to display a grid, we send a request to the server with jQuery's $.ajax and on the server we query the DB, perform some stuff and then convert the data from the DB to a json object, then we respond that object to the client and BAM! done.
All this is donde superb and the Net Panel catches all this requests/responds and shows the time, the amount of data (KB / MB), parameters etc etc.
But sometimes, all of this is performed, the data is already displayed on the page but on the Net Panel the loading image is still spinning and never stops, if i go and debug the js of the jQuery's $.ajax => success: function, i hit the breakpoints and all of that, but the .Net Panel is still spinning.
I've tried to catch the culprit, whether it's a bad json / xml, a timeout ( unlikely because the most heavy transaction is merely 4 seconds ), you name it. And the funny thing is it doesn't shows up in the same request. For example, i have Button A and Button B, i press B-A and Net Panel spins and stops, press B-B Net Panel Spins and stops, play a little with those buttons and BAM, a never ending spinning is there, GOTCHAS: i don't push the buttons until a response has finished ( Data is displayed on the page ) so don't think i'm mashing the buttons non-stop.
Anyway, it's no biggie, just something that is a little annoying because it seems to know when i want to get the time of the request to spin until eternity.
Oh and another thing, on the Console Panel it always spins and stops no matter what, so, i've been using that panel lately, but i am constantly clearing it because it grows like there's no tomorrow with all the js debbuging and stuff.
Thanks!
Sebo
Aug 19, 2011, 6:08:03 AM8/19/11
to Firebug, odv...@gmail.com
Hi Sam!
On Aug 9, 8:30 pm, Sam <sam....@gmail.com> wrote:
> Hey folks!
>
> Guys, terrific work with this tool, i really appreciate all the efforts
> given to this and specially to the attention to users, Man! you must be
> close to Gandhi when it comes to patience to deal with all of us.
Great, right for this answer we took 10 days. :-( Sorry for the delay,
"staff" is not that big at the moment.
Sounds definitely like a bug. Unfortunately without a reproducible
test case we won't be able to solve that problem.
So, as I am reading you can currently not see any pattern in when this
happens and when not?
> Anyway, it's no biggie, just something that is a little annoying because it
> seems to know when i want to get the time of the request to spin until
> eternity.
Non-the-less it's good you posted it, because others will surely have
the same problem.
As said before we just need to be able to track it down to a simple
test case. Otherwise we could try to change something, but can't say,
if that fixes the problem.
> Oh and another thing, on the Console Panel it always spins and stops no
> matter what, so, i've been using that panel lately, but i am constantly
> clearing it because it grows like there's no tomorrow with all the js
> debbuging and stuff.
Ok, sounds like only the Net panel is involved. If so, that would
already narrow the area to search a bit.
Maybe the event, that the request was loaded completely, is not
triggered for some reason.
> Thanks!
You're welcome!
Sebastian
On Aug 9, 8:30 pm, Sam <sam....@gmail.com> wrote:
> Hey folks!
>
> Guys, terrific work with this tool, i really appreciate all the efforts
> given to this and specially to the attention to users, Man! you must be
> close to Gandhi when it comes to patience to deal with all of us.
"staff" is not that big at the moment.
test case we won't be able to solve that problem.
So, as I am reading you can currently not see any pattern in when this
happens and when not?
> Anyway, it's no biggie, just something that is a little annoying because it
> seems to know when i want to get the time of the request to spin until
> eternity.
the same problem.
As said before we just need to be able to track it down to a simple
test case. Otherwise we could try to change something, but can't say,
if that fixes the problem.
> Oh and another thing, on the Console Panel it always spins and stops no
> matter what, so, i've been using that panel lately, but i am constantly
> clearing it because it grows like there's no tomorrow with all the js
> debbuging and stuff.
already narrow the area to search a bit.
Maybe the event, that the request was loaded completely, is not
triggered for some reason.
> Thanks!
You're welcome!
Sebastian
Justin J Query IV
Aug 23, 2011, 2:16:17 AM8/23/11
to Firebug
Just had the same problem.
Added 'cache:false' to my ajax call
Problem went away.
For reference:
This was generally on the first ajax call out. It would show two
identical ajax calls - but only 1 ever hit the server. On subsequent
triggering of the same call
it would only show one request in firebug.
I was appending my own unique string to the URL before switching to
'cache:false' - essentially the same thing cache:false does. However
there may be something else going on with the jquery cache:false
option that affects how the call get sent - so possibly a jquery issue
instead of a firebug issue.
Added 'cache:false' to my ajax call
Problem went away.
For reference:
This was generally on the first ajax call out. It would show two
identical ajax calls - but only 1 ever hit the server. On subsequent
triggering of the same call
it would only show one request in firebug.
I was appending my own unique string to the URL before switching to
'cache:false' - essentially the same thing cache:false does. However
there may be something else going on with the jquery cache:false
option that affects how the call get sent - so possibly a jquery issue
instead of a firebug issue.
Sam Ccp
Aug 23, 2011, 1:28:46 PM8/23/11
to fir...@googlegroups.com
Hello Justin, Sebo.
Last week i was on vacations so i couldn't reply on your thoughtful comment Sebo, thanks!
Justin, I just tried this approach and while it indeed prevents a few "ghost" requests, it still happens from time to time, i'm making a test case so you guys could play with it and try to figure out what's shaking.
Anyway, thanks guys, have an awesome day.
--
Last week i was on vacations so i couldn't reply on your thoughtful comment Sebo, thanks!
Justin, I just tried this approach and while it indeed prevents a few "ghost" requests, it still happens from time to time, i'm making a test case so you guys could play with it and try to figure out what's shaking.
Anyway, thanks guys, have an awesome day.
--
You received this message because you are subscribed to the Google Groups "Firebug" group.
To post to this group, send email to fir...@googlegroups.com.
To unsubscribe from this group, send email to firebug+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
--
"Do something worth remembering."
-Elvis Presley-
Reply all
Reply to author
Forward
0 new messages