This is already reported in issue 5684 
<https://code.google.com/p/fbug/issues/detail?id=5684>. It would be great 
if you could attach a test case for both, long loading and aborted requests 
to it.

Sebastian

On Wednesday, July 16, 2014 2:12:01 PM UTC+2, Kumar Harsh Srivastava wrote:
>
> I'm not sure how I'll post a test-case for this. We'll basically need to 
> make an AJAX request which takes a long time to complete (or gets stuck on 
> the serverside), so that no response comes for enough time that we can open 
> firebug and test this occurence.
>
>
> On Wednesday, 16 July 2014 17:17:06 UTC+5:30, Jan Honza Odvarko wrote:
>>
>> This might be possible to fix.
>>
>> Do you have an online test case that we could use to test it?
>> Can you file a bug (or is there one already?) and attach the test case?
>> https://code.google.com/p/fbug/issues/list
>>
>> Thanks
>> Honza
>>
>>
>> On Wednesday, July 16, 2014 8:58:51 AM UTC+2, Kumar Harsh Srivastava 
>> wrote:
>>>
>>> In firebug's Net panel, if I click on a request row, it shows the 
>>> request headers, body and response, etc.
>>> But if the request is still* pending*, (say server is stuck somewhere, 
>>> or some error in my code), firebug shows *NOTHING*. When I hover over 
>>> the URL row, it just shows the full URL, but it's *not clickable*, so I 
>>> cannot view the request sent at all. The request is shown only when the 
>>> request *times-out*, which understandable takes a looooong time to 
>>> come... (or I have to manually crash my server so that firebug shows what 
>>> requests were sent, which is pretty stupid)
>>>
>>> In the Chrome Deveopler Tools, or even in Firefox's Developer Tools, 
>>> when I select a pending request, the "provisional" data is shown. This is 
>>> of great help, as it permits me to immediately start searching for possible 
>>> bugs in my code, rather than waiting for a timeout.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Firebug" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/firebug.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/firebug/6b6a736c-7611-48dc-8255-d137660ad433%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to