Request blocked by ETP is wrongly labeled as "blocked by devtools"
Categories
(DevTools :: Console, defect, P3)
Tracking
(firefox128 fixed)
| Tracking | Status | |
|---|---|---|
| firefox128 | --- | fixed |
People
(Reporter: jdescottes, Assigned: nchevobbe)
References
Details
Attachments
(1 file)
STRs:
- open https://vigilant-su-96.deno.dev/profile
- open netmonitor
- select a value in the dropdown
- click submit
A request will be shown as blocked in the netmonitor. If you go to the console and find the request as well, hovering on the blocked icon will show "blocked by devtools". But this request is actually blocked due to ETP being enabled.
Also, when disabling ETP, the same request contains very helpful information in the netmonitor sidepanel to know that the request "would" have been blocked if ETP was enabled. However when ETP is on, there is no information explaining why the request is blocked.
|
Reporter | |
Updated•4 months ago
|
|
Assignee | |
Comment 1•4 months ago
|
||
Requests can be blocked because of many reasons, but the label was always
saying it was because of DevTools.
Update the label so we follow what's done in Netmonitor.
|
||
Updated•4 months ago
|
Pushed by nchevobbe@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/e80fd0474f93 [devtools] Update network request blocked string. r=devtools-reviewers,ochameau.
|
|
Reporter | |
Comment 3•4 months ago
|
||
For reference, we filed another bug to check why the blocking details are not displayed when the request is actually blocked: Bug 1896858
Description
•