Closed
Bug 964977
Opened 10 years ago
Closed 10 years ago
Infer JSON from response
Categories
(DevTools :: Netmonitor, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 30
People
(Reporter: rcampbell, Assigned: vporof)
Details
(Whiteboard: [chrome-parity] [qa-])
Attachments
(1 file)
|
12.64 KB,
patch
|
rcampbell
:
review+
|
Details | Diff | Splinter Review |
possibly related to bug 859138. We should do better at inferring when a response is JSON but returned as with plaintext MIME type. See Firebug / Chrome.
|
Assignee | |
Comment 1•10 years ago
|
||
We could... brutally do a JSON.parse on plain-text responses and see what happens? :)
|
|
Assignee | |
Comment 2•10 years ago
|
||
|
Reporter | |
Comment 3•10 years ago
|
||
Comment on attachment 8369052 [details] [diff] [review] v1 Review of attachment 8369052 [details] [diff] [review]: ----------------------------------------------------------------- looks good
Attachment #8369052 -
Flags: review?(rcampbell) → review+
|
|
Assignee | |
Comment 4•10 years ago
|
||
https://hg.mozilla.org/integration/fx-team/rev/118701a7fadd
Whiteboard: [chrome-parity] → [chrome-parity][fixed-in-fx-team]
|
||
Comment 5•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/118701a7fadd
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Whiteboard: [chrome-parity][fixed-in-fx-team] → [chrome-parity]
Target Milestone: --- → Firefox 30
|
||
Updated•10 years ago
|
Whiteboard: [chrome-parity] → [chrome-parity] [qa-]
|
||
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•