Visual glitch on the devtools network timing
Categories
(DevTools :: Netmonitor, defect, P2)
Tracking
(firefox-esr115 unaffected, firefox123 wontfix, firefox124 wontfix, firefox125 fix-optional)
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox123 | --- | wontfix |
firefox124 | --- | wontfix |
firefox125 | --- | fix-optional |
People
(Reporter: esroyo, Assigned: bomsy)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: nightly-community, regression)
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:123.0) Gecko/20100101 Firefox/123.0
Steps to reproduce:
Visit a website a couple of times so that the request is cached on the client.
--
Probably reproducible by visiting: https://esroyo.github.io/systemjs.sh-examples/dist/index.html
Attached screenshot corresponds to the 5th request GET https://systemjs.sh/vue
.
Actual results:
The server-timing response headers are displayed out of position in the details of the request.
Expected results:
Either they are ignored, or take the right space.
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.
Comment 2•1 year ago
|
||
Str:
- Open
Inspector
-Network
- Open https://esroyo.github.io/systemjs.sh-examples/dist/index.html
- Click on GET https://systemjs.sh/vue on the network
- Click on
Timings
tab
If not reproduced, proceed to the next step: - Press F5 key to reload
- Click on GET https://systemjs.sh/vue on the network
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=fdee7bc5d06a921a63a9cd74c65c8fbd96d18cf4&tochange=94a07cbcc6f95874dd7b02220f0f7229b60c076b
Updated•1 year ago
|
Comment 3•1 year ago
|
||
:bomsy, since you are the author of the regressor, bug 1353798, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Comment 4•11 months ago
|
||
Honza, can you please apply Priority/Severity settings to this report when you get a chance? It will help with release management's triage.
Comment 5•11 months ago
•
|
||
Adding flag to triage this at our weekly meeting.
I can reproduce the problem on my machine (Win11) easily by following STRs in comment #2
Bomsy, the regression points to bug 1353798. Is that the culprit?
Updated•11 months ago
|
Updated•11 months ago
|
Updated•11 months ago
|
Updated•10 months ago
|
Assignee | ||
Comment 6•10 months ago
|
||
Thanks .. looking into this.
Assignee | ||
Comment 7•10 months ago
|
||
Note: This happens when cached is disabled.
Assignee | ||
Comment 8•10 months ago
|
||
Description
•