Dev Tools Network Response tab rendered HTML page no longer responds to clicks
Categories
(DevTools :: Netmonitor, defect)
Tracking
(firefox-esr102 unaffected, firefox108 wontfix, firefox109 wontfix, firefox110 affected)
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox108 | --- | wontfix |
firefox109 | --- | wontfix |
firefox110 | --- | affected |
People
(Reporter: NinjaMeTimbers, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
157.77 KB,
image/jpeg
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:108.0) Gecko/20100101 Firefox/108.0
Steps to reproduce:
I develop an internal web app using Python/Django for the server side. By default Django sends a nicely formatted debug error page. Often I will get these debug messages from requests send through an ajax request, so they show up on the Network tab of the Developer Tools. These debug pages have some parts that expand when you click on them (for example to show the local vars in the traceback). As of recently, clicking on items on the network response preview does not do anything, so I can't see the local variables at the point of crash. I can't open the response in a new tab because the page won't work there because the csrf verification will fail, so I need to be able to access it right in the Response panel.
Actual results:
I click on the Dev Tools Network Response tab contents and nothing happens, when it used to as of a couple months ago. For example clicking on the Local vars part of the returned debug page currently does nothing.
Expected results:
The onclick event in the response page should have fired which would have expanded the Local vars so that they would be displayed.
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'DevTools::Netmonitor' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•3 years ago
|
||
I was about to submit a bug but this might be the same one.
Since the version 109 I can no longer select the rendered response text. I can still the raw response text, but not the rendered one.
I rely on this to copy some of the text to look for solutions.
Comment 3•3 years ago
|
||
Do you know if those "expandable" sections are done with pure HTML (eg <details>
element) or if they use javascript? We disabled javascript for the previews for security reasons, I doubt we would re-enable it.
But if they are using pure HTML then, this issue is the same as Bug 1800916, which should also cover the report from comment #2
Updated•3 years ago
|
Comment 4•3 years ago
|
||
Set release status flags based on info from the regressing bug 1640689
Updated•3 years ago
|
Comment 6•3 years ago
|
||
:ochameau, since you are the author of the regressor, bug 1640689, could you take a look? Also, could you set the severity field?
For more information, please visit auto_nag documentation.
Comment 7•3 years ago
|
||
(In reply to NinjaMeTimbers from comment #5)
Yeah it uses onclick events.
Any chance you can check on Chrome? curious to see if they are supporting this
Reporter | ||
Comment 8•3 years ago
|
||
(In reply to Julian Descottes [:jdescottes] from comment #7)
(In reply to NinjaMeTimbers from comment #5)
Yeah it uses onclick events.
Any chance you can check on Chrome? curious to see if they are supporting this
Yes, it still works in Chrome.
Comment 9•3 years ago
|
||
(In reply to NinjaMeTimbers from comment #8)
(In reply to Julian Descottes [:jdescottes] from comment #7)
(In reply to NinjaMeTimbers from comment #5)
Yeah it uses onclick events.
Any chance you can check on Chrome? curious to see if they are supporting this
Yes, it still works in Chrome.
I just tried a basic page using an onclick event handler and the handler is not executed in the netmonitor preview in Chrome or Firefox.
So I looked up the Django source code and the "Local vars" link here is a <details>
element: https://github.com/django/django/blob/main/django/views/templates/technical_500.html#L263-L264
<details>
<summary class="commands">Local vars</summary>
Closing as a duplicate of Bug 1800916, this is the same root cause.
Description
•