[Webkit-unassigned] [Bug 28119] New: Debugging XHR requests in the Web Inspector

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=28119

           Summary: Debugging XHR requests in the Web Inspector
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Enhancement
          Priority: P2
         Component: Web Inspector
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: alex at prohost.com.au


Note: This ticket is really a starting point for many tickets.  

We develop web applications which load from a single page load and from then,
everything is run via XHR requests using the ExtJS javascript library.

In order to be able to debug xhr heavy applications there are several features
that firebug provides that prevents us using webkit (even though we prefer
webkit because of it's sheer speed).

The following features is the critical missing feature in our view:
a) Unable to see the post, put or delete variables when making an XHR request.

When you make a POST, PUT, DELETE, GET in firebug the first tab is a params tab
which nicely formats all of the parameters your' XHR request is sending. 
Allowing you to quickly debug what is happening.


Nice features that firebug has:
------------------------------------
a) JSON formatting of responses (makes it much easier to debug)
b) Ability to see XHR requests inline, and inspect each one
c) being able to see the XHR requests in a big list in the sequential order
they we're called
d) being able to see from the main console whether a request has finished or
not.
e) The ability to see the response code, and highlighting the request in red if
the response code is not ok (i.e. if it's a 500)
f) all the copying options (copy, copy response body).  This is really useful
if you need to external debugging or copying and pasting into unit tests. In
particular the right click copy on the JSON tab to get formatted json is really
good.  The ability to do this both in the request body and the response would
be nice (firebug can only do the response)

Viewing Rendered Response
----------------------
One feature that firebug does not have that would be really awesome, would be
the ability to either middle click on the response (to open in a new tab) and
have the new tab perform the exact action the request did (whether it was a
POST, GET or DELETE) and load up the response text.  This would be very usefull
for reading the response of XHR requests that cause server side errors. 
Currently if firebug returns a 500, we have to basically read through the
response as html source to read the error message. So someway of rendering that
content would be nice.

Essentially the XHR tracking of firebug is near perfect for ajax heavy
applications apart from it's other speed issues. 

Example:
-----------
http://ccinct.com/lab/filter-grid/
This can be used to fire of various ajax requests (although the data is broken
so it doesn't return any data into the widget).  But for seeing the requests
it's fine.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.