Open Bug 1484005 Opened 6 years ago Updated 8 months ago

[meta] Display detailed blocked/rejected/failed/broken requests

Categories

(DevTools :: Netmonitor, enhancement, P2)

enhancement

Tracking

(Not tracked)

People

(Reporter: Harald, Unassigned)

References

(Depends on 14 open bugs, Blocks 1 open bug)

Details

(Keywords: meta)

User Story

When I audit a site's network dependencies,
I need to see which resources are (potentially) affected by content blocking,
so that I can code defensively against breakage caused by blocked resources.
No description provided.
Depends on: 1333994
Blocks: 1462372
Depends on: 1510817
Depends on: 1556451
Summary: [meta] Improve content blocking debugging flow → [meta] Content Blocking & CORS
Summary: [meta] Content Blocking & CORS → [meta] Request Blocking & Tracking Protection & CORS

If you now are logged in to your line, and the browser would let the page to enter your credentials (session cookie), the shift would be accepted.
https://www.taxiinreading.com/

Priority: -- → P2
Summary: [meta] Request Blocking & Tracking Protection & CORS → [meta] Display detailed blocked/rejected/failed requests
Depends on: 1553026
Depends on: 1552997
Depends on: 1445637
Depends on: 1629875
Depends on: 1524531
Depends on: 1555057
Depends on: 1564011
No longer depends on: 1410793
Depends on: 1591807
Depends on: 1493599
Depends on: 1638313
Depends on: 1635460
Depends on: 1671147
Depends on: 1682153
Depends on: 1683672
Severity: normal → S3
Depends on: 1849946
Summary: [meta] Display detailed blocked/rejected/failed requests → [meta] Display detailed blocked/rejected/failed/broken requests
No longer blocks: 1884571
Depends on: 1884571
Depends on: 1885799
You need to log in before you can comment on or make changes to this bug.