Open
Bug 1565049
Opened 6 years ago
Updated 3 years ago
Blocked storage warnings should link to the source location when possible
Categories
(DevTools :: Console, enhancement, P3)
DevTools
Console
Tracking
(Not tracked)
NEW
People
(Reporter: Harald, Unassigned)
Details
User Story
When hitting a content blocking warning about blocked storage access, I want to have a reference to the script location that triggered the storage access, so that I can debug the impact.
Attachments
(1 file)
|
53.60 KB,
image/png
|
Details |
Link to enter_bug.cgi is not useful to debug this warning
Follow up from https://bugzilla.mozilla.org/show_bug.cgi?id=1563388#c6 , which points out how hard it is to know what kind of storage access was blocked.
Tracking protection warnings have very little context, beyond mentioning the script that triggered the warning.
Whenever possible, we should link to the script location that triggered the storage access warning, so developers don't have to audit the whole file for storage API use.
|
||
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•