1555647 - Display of raw or formatted response should be persistent

Status: RESOLVED FIXED

(DevTools :: Netmonitor, enhancement, P3)

Description

[123Knuckles]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:67.0) Gecko/20100101 Firefox/67.0

Steps to reproduce:

open the network tab while accessing a page, and then inspect a particular request, and select the "response" tab.

Actual results:

You get a preview of the response content

Expected results:

get the plain text of the response.

You already have a preview of the page in the main browser itself, you're inspecting the response because you're highly likely a developer who is interested in looking one layer below. Typically, you want to look at the raw response because something is wrong and you're debugging/troubleshooting it.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The priority flag is not set for this bug.
:Honza, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 2

[Jan Honza Odvarko [:Honza] (always need-info? me)]

Thanks for the report!

@123Knuckles: if you collapse the Preview section you can see raw Response payload section. So, if the collapsed/expanded state of these section would be persistent across reloads (and perhaps Firefox sessions) it would solve the problem, correct?

Honza

Comment 3

[123Knuckles]

(In reply to Jan Honza Odvarko [:Honza] (always need-info? me) from comment #2)

Thanks for the report!

@123Knuckles: if you collapse the Preview section you can see raw Response payload section. So, if the collapsed/expanded state of these section would be persistent across reloads (and perhaps Firefox sessions) it would solve the problem, correct?

Honza

Yes, That would certainly be sufficient. Thanks.

Comment 4

[Sebastian Zartner [:sebo]]

As the display changed to a toggle button instead of collapsible panes in bug 1651649, I've changed the summary accordingly.
I've also tested this on Firefox 109 and verified that the raw or formatted display is still not persisted.

Here are some updated steps to reproduce what is expected:

1. Open the Netmonitor on this page
2. Reload the page
3. Select the page request
4. Switch to the Response tab
5. Click the Raw toggle to activate it
6. Switch to the Request tab and back to the Response tab
   ⇒ The Raw toggle should still be active.
7. Reload the page
8. Select the page request again
   ⇒ The Raw toggle should still be active.

Optional:

9. Close and open the browser
10. Repeat steps 1 to 4
    ⇒ The Raw toggle should still be active.

For what it's worth, there's also a related post asking for this on Stack Overflow.

Sebastian

Comment 5

[mozilla.frank]

I was wondering if there is any update on this? I find it very debilitating to click the Raw button every single time.

Please, please, please, make the state of the Raw button persistently 'ON' because showing rendered content in the developer tool is not useful in any use case.

As a work around I am currently not using Firefox DevTools as my main debugging tool. I had to switch to a different web browser for this and might not switch back to Firefox. For certain checks I do have to use the Firefox DevTools and every single time I run into this issue. I am probably not the only one having this problem?

Comment 6

[Nicolas Chevobbe [:nchevobbe]]

Attachment: Bug 1555647 - [devtools] Persist Response raw toggle state. r=#devtools.

Comment 7

[Nicolas Chevobbe [:nchevobbe]]

(In reply to mozilla.frank from comment #5)

I was wondering if there is any update on this? I find it very debilitating to click the Raw button every single time.

Please, please, please, make the state of the Raw button persistently 'ON' because showing rendered content in the developer tool is not useful in any use case.

As a work around I am currently not using Firefox DevTools as my main debugging tool. I had to switch to a different web browser for this and might not switch back to Firefox. For certain checks I do have to use the Firefox DevTools and every single time I run into this issue. I am probably not the only one having this problem?

I quickly put up a small patch to persist the raw toggle value. This is something we got feedback on from someone else as well this week, so we'll try to push it over the finish line (my patch needs tests and making sure it doesn't break the other interaction where we force the toggle to be set to true)

Comment 8

[mozilla.frank]

Thank you very much for looking into this. I am looking forward to seeing this feature in a next version. It would make a huge difference to me and I presume also to others.

Comment 9

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/5def652c9bdf
[devtools] Persist Response raw toggle state. r=devtools-reviewers,bomsy.

Comment 10

[Sandor Molnar[:smolnar]]

https://hg.mozilla.org/mozilla-central/rev/5def652c9bdf