Closed Bug 1347934 Opened 7 years ago Closed 6 years ago

Not possible to expand XHR JSON array/object to show its contents in Console

Categories

(DevTools :: Console, defect, P3)

52 Branch
defect

Tracking

(firefox52 wontfix, firefox-esr52 wontfix, firefox53 wontfix, firefox54 wontfix, firefox56 wontfix, firefox57 wontfix)

RESOLVED INVALID
Tracking Status
firefox52 --- wontfix
firefox-esr52 --- wontfix
firefox53 --- wontfix
firefox54 --- wontfix
firefox56 --- wontfix
firefox57 --- wontfix

People

(Reporter: byja, Unassigned)

References

Details

(Keywords: regression)

Attachments

(2 files)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20170302120751

Steps to reproduce:

Bring up Dev Tools, select Console.
Under NET, tick XHR to show page requests.
Page makes a request, GET or POST with url.
Click on "Disclosure Triangle"
Select Response tab
Expand JSON
When there is object or array, click on Disclosure Triangle, everything gets collapsed to GET/POST url


Actual results:

Everything collapses to XHR node, and needs to be expanded again.


Expected results:

JSON array or object should be expanded to show its contents when you click on either Disclosure Triangle or array/object name/ref.
Component: Untriaged → Developer Tools: Console
Attached file sample.json
Attached file 1347934.html
AFAIK, the Net panel for requests in the Console has been removed in Nightly, there is only Netmonitor and JSON object/arrays are expanded correctly in Nightly.
Summary: Dev tools console xhr json navigation → Not possible to expand XHR JSON array/object to show its contents in Console
That said, it's a regression in FF52:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=feb1c52ebe9ef8cff09dea275aa06d9441f5fe93&tochange=500baee3ce9f1b701ace9d38489cbc112d076c72

Patrick Brosset — Bug 1304685 - Show empty text nodes in markupview if they impact layout; r=jdescottes
Blocks: 1304685
Status: UNCONFIRMED → NEW
Has Regression Range: --- → yes
Has STR: --- → yes
Ever confirmed: true
Flags: needinfo?(pbrosset)
Keywords: regression
OS: Unspecified → All
Hardware: Unspecified → All
Regression window seems wrong, I just tried with a changeset preceeding Bug 1304685 (687572ea20cb) and the issue already occurs.
No longer blocks: 1304685
Flags: needinfo?(pbrosset)
Because you forgot to disable the new frontend for the console. You need to run mozregression with the command --pref "devtools.webconsole.new-frontend-enabled:false".

Could you test again, please.
Flags: needinfo?(jdescottes)
(In reply to Loic from comment #6)
> Because you forgot to disable the new frontend for the console. You need to
> run mozregression with the command --pref
> "devtools.webconsole.new-frontend-enabled:false".

I did test with the old console frontend.
I could not have reproduced the bug otherwise, this feature is not implemented in the new console.

> Could you test again, please.

Just did a bisect and the regression comes from https://hg.mozilla.org/mozilla-central/rev/cf0fc7add23c which is for Bug 1306840.

It's actually in the regression window you linked. Since this bug was blocked specifically on Bug 1304685, I thought the regression window only contained the changeset for this bug. But it was not the case and I didn't check the link. Sorry about that.
Blocks: 1306840
Flags: needinfo?(jdescottes)
Ah, I see, I guessed wrongly the regressing bug was bug 1304685. :)
Priority: -- → P3
It's too late for 54. Mark 54 won't fix.
Product: Firefox → DevTools
Not valid anymore since we're using netmonitor components
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: