Thanks for the screenshots, Kumar. I added some notes <https://code.google.com/p/fbug/issues/detail?id=5684#c5> about this to issue 5684.
Sebastian On Friday, July 18, 2014 2:11:20 PM UTC+2, Kumar Harsh Srivastava wrote: > > here are some screenshots to make it a little more clear what I'm talking > about: > > I'm numbering and attaching it as google-groups is not able to attach all > of them in their right places... > > 1. First image shows how Firebug shows it. > 2. Me inspecting normal URLs (who have received the response) > 3. Me trying to inspect URLs who have failed OR who are still waiting for > a response. > 4. Me SUCCESSFULLY being able to see the request parameters in the Firefox > Developer Tools Network Tab. > 5. Me Trying Chrome DevTools. > 6. Me SUCCESSFULLY being able to see the request parameters in the Chrome > DevTools (Note the red box: "Provisional Headers are Shown" > > Firefox and Chrome show me what was sent, Headers, Query Params, Cookies, > etc... > Firebug doesn't even let me click on the URL waiting for a response. > > > > > > > > On Friday, 18 July 2014 15:45:49 UTC+5:30, Kumar Harsh Srivastava wrote: >> >> Hi Jan, >> >> But that is NOT what I'm asking about at all. >> >> I'm asking why doesn't firebug show the "*SENT REQUESTS*" when the >> response hasn't come? Chrome DevTools and Firefox's built-in DevTools show >> the requests. (It's labelled as 'provisional requests' or something in >> Chrome), but the point is that they show, and firebug shows nothing while >> waiting for the response. >> >> If for example, the response never comes, I can't even go to Firebug and >> see what Requests were sent. It's impossible. >> So, I have to open Chrome or the native dev-tools and try to recreate the >> scenario. >> >> >> >> On Friday, 18 July 2014 13:28:24 UTC+5:30, Jan Honza Odvarko wrote: >>> >>> On Wednesday, July 16, 2014 3:24:17 PM UTC+2, Kumar Harsh Srivastava >>> wrote: >>>> >>>> OK. Try these files. (Lifted from w3schools' example for Ajax with PHP >>>> Servers) >>>> >>>> If your server is fast, maybe you'll not get enough time before >>>> response comes, in that case, just increase the number of items in the >>>> array, or remove the echo at the end. >>>> >>> >>> >>> I tried the test case and I think that the problem is that you are >>> sending the result at the end of the process, if you *flush* the response >>> buffer during the computation (using flush() PHP API), Firebug properly >>> shows the response as it's coming. >>> >>> See also my comment here: >>> https://code.google.com/p/fbug/issues/detail?id=5684#c3 >>> >>> Honza >>> >>> >>> >>> -- 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/71334660-3380-4a8e-a285-f9ceba2005fd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
