Bug 121723

Summary: Web Inspector: Format JSON for request just like responses
Product: WebKit Reporter: Timothy Hatcher <timothy>
Component: Web InspectorAssignee: Timothy Hatcher <timothy>
Status: RESOLVED FIXED    
Severity: Normal CC: commit-queue, graouts, joepeck, timothy, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
Patch none

Timothy Hatcher
Reported 2013-09-20 15:48:24 PDT
<rdar://problem/15028708> When viewing a JSON response from the server it is auto-formatted with {} functionality. When sending a JSON request it is not auto formatted. The {} functionality is greyed out. Both request and response have the "Content-Type application/json;charset=UTF-8" header. Steps to Reproduce: 1. Go to the network requests in timeline. 2. Send out a JSON request with a server JSON response which bot have "Content-Type application/json;charset=UTF-8" header 3. View JSON response: Beautifully formatted. 4. View JSON request: Not formatted and no option to format it. Greyed out {} button. Expected Results: Beautifully formatted JSON request. Actual Results: Raw unformatted JSON
Attachments
Patch (10.60 KB, patch)
2013-09-20 15:54 PDT, Timothy Hatcher
no flags
Timothy Hatcher
Comment 1 2013-09-20 15:54:52 PDT
Joseph Pecoraro
Comment 2 2013-09-20 16:21:19 PDT
Comment on attachment 212231 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=212231&action=review Nice! r=me > Source/WebInspectorUI/UserInterface/Utilities.js:1146 > + if (subparts[0].toLowerCase() === "boundary") > + boundary = subparts[1]; > + else if (subparts[0].toLowerCase() === "charset") Nit: Avoid duplicate toLowerCase()?
WebKit Commit Bot
Comment 3 2013-09-20 16:44:16 PDT
Comment on attachment 212231 [details] Patch Clearing flags on attachment: 212231 Committed r156209: <http://trac.webkit.org/changeset/156209>
WebKit Commit Bot
Comment 4 2013-09-20 16:44:18 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.