Developer Tools: Network status bar is misplaced after switching tabs
Categories
(DevTools :: Netmonitor, defect, P2)
Tracking
(firefox-esr115 unaffected, firefox-esr128 wontfix, firefox121 wontfix, firefox122 wontfix, firefox123 wontfix, firefox124 wontfix, firefox129 wontfix, firefox130 wontfix, firefox131 fixed)
People
(Reporter: Perlence, Assigned: jdescottes)
References
(Regression)
Details
(Keywords: regression)
Attachments
(3 files)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:121.0) Gecko/20100101 Firefox/121.0
Steps to reproduce:
- Open the Developer Tools
- Click on the Network tab
- Click on a request, the request details sidebar opens
- Click any other Developer Tools tab, e.g. Debugger
- Click on the Network tab again
Actual results:
The status bar of the request table moves up, see the screenshot.
Expected results:
The status bar stays at the bottom of the request table.
Comment 1•1 year 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.
Reporter | ||
Updated•1 year ago
|
Comment 2•1 year ago
|
||
Thanks for the report, I can indeed reproduce
/*
* Removing onResize() method causes perf regression - too many repaints of the panel.
* So it is needed in ComponentDidMount and ComponentDidUpdate. See Bug 1532914.
*/
onResize() {
const parent = this.refs.scrollEl.parentNode;
this.refs.scrollEl.style.width = parent.offsetWidth + "px";
this.refs.scrollEl.style.height = parent.offsetHeight + "px";
}
Comment 3•1 year ago
|
||
I can't reproduce on ESR 115
Comment 4•1 year ago
|
||
Bug 1451717 caused this issue to appear, but it may just be that we used to benefit from an erroneous behavior before.
Comment 5•1 year ago
|
||
Set release status flags based on info from the regressing bug 1451717
:emilio, since you are the author of the regressor, bug 1451717, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
Comment 6•1 year ago
|
||
I don't think this should be slower than what you're doing nowadays. If
for some reason we do need this, it should use a resize observer on the
container, not listen to the window resize event.
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Comment 7•1 year ago
|
||
Set release status flags based on info from the regressing bug 1451717
Updated•1 year ago
|
Updated•1 year ago
|
Assignee | ||
Comment 9•9 months ago
|
||
Comment 10•7 months ago
|
||
Updated•7 months ago
|
Comment 11•7 months ago
|
||
bugherder |
Updated•7 months ago
|
Description
•