Open
Bug 1462884
Opened 6 years ago
Updated 2 years ago
Status code flag sometimes doesn't work
Categories
(DevTools :: Netmonitor, defect, P3)
DevTools
Netmonitor
Tracking
(Not tracked)
NEW
People
(Reporter: ntim, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: regression, regressionwindow-wanted)
Attachments
(2 files)
Sometimes typing "status-code:200" doesn't show all requests with status-code 200, even though it's being autocompleted.
I'm thinking this is because strict equality is failing here: https://searchfox.org/mozilla-central/source/devtools/client/netmonitor/src/utils/filter-text-utils.js#117
in some cases.
Comment 1•6 years ago
|
||
Thanks for the report Tim!
Anyone can reproduce this issue?
It would be great to have steps-to-reproduce.
Honza
Has STR: --- → no
Priority: -- → P3
Comment 2•6 years ago
|
||
Hi guys, i tried reproducing this issue using a few versions of Firefox including the latest version of nightly on a windows 10, and i used http://ro.ign.com/console
I couldn't manage to reproduce this issue, however it does seem to happen sometimes with some "cached" requests.
In this example there are a few cached 301 status code request that are no longer displayed once the user filters for "status-code:301" Please see Attachments.
Steps to Reproduce :
1. Open Firefox and reach http://ro.ign.com/console
2. Open Dev Tools and Click the "Console" link from the top
3. Wait for the page to reload.
4. Scroll in order to find the 301 codes requests in dev tools.
5. Filter Url's with "status-code:301"
Expected results :
The 301 requests should be displayed when they are filtered using the Auto Complete "status-code:301"
Actual results :
The Network tab is blank .
Please note that sometimes when the user refreshes the page the 301 requests are properly displayed after the user filters the tab.
Also note that the 200 code |requests are not displayed if they are cached and the user filters for them.
Comment 3•6 years ago
|
||
Comment 4•6 years ago
|
||
Reporter | ||
Comment 5•6 years ago
|
||
Yes, this happens with cached requests mainly.
I don't really have an exact STR, but globally, it's load a website with a couple of cached requests, then use the status-code:XXX filter flag.
Updated•6 years ago
|
Product: Firefox → DevTools
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•