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

NEW
Unassigned

Status

P3
normal
2 years ago
4 months ago

People

(Reporter: byja, Unassigned)

Tracking

({regression})

52 Branch
regression

Firefox Tracking Flags

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

Details

Attachments

(2 attachments)

169 bytes, text/plain
Details
218 bytes, text/html
Details
(Reporter)

Description

2 years ago
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.

Updated

2 years ago
Component: Untriaged → Developer Tools: Console

Comment 1

2 years ago
Created attachment 8848757 [details]
sample.json

Comment 2

2 years ago
Created attachment 8848758 [details]
1347934.html

Comment 3

2 years ago
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

Comment 4

2 years ago
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
status-firefox52: --- → affected
status-firefox53: --- → affected
status-firefox54: --- → affected
status-firefox55: --- → affected
status-firefox-esr52: --- → affected
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)
Keywords: regressionwindow-wanted

Comment 6

2 years ago
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)
Keywords: regressionwindow-wanted

Comment 8

2 years ago
Ah, I see, I guessed wrongly the regressing bug was bug 1304685. :)
status-firefox52: affected → wontfix
status-firefox53: affected → wontfix
status-firefox-esr52: affected → fix-optional
Priority: -- → P3
It's too late for 54. Mark 54 won't fix.
status-firefox54: affected → wontfix
status-firefox55: affected → wontfix
status-firefox56: --- → wontfix
status-firefox57: --- → fix-optional

Updated

4 months ago
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.