Open
Bug 1610455
Opened 5 years ago
Updated 6 months ago
Record content blocking log when a window is in-process
Categories
(Core :: Privacy: Anti-Tracking, defect, P3)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox74 | --- | affected |
People
(Reporter: dimi, Unassigned)
References
Details
Right now, when WindowGlobalParent is created in-process, we don't record content blocking log because we thought there shouldn't be such a case[link].
In Bug 1609144, we found out there were cases tracker are loaded in in-process windows. For example:
- Developer tools -> Network Panel -> Click on a request with trackers -> Response
- View Page Info -> Media
There might be the other cases.
This bug is to discuss if we should record content blocking log when it is in-process.
Comment 1•5 years ago
|
||
I think we can just throw the data away in those cases, personally.
Comment 2•5 years ago
|
||
Can you please explain in more detail what causes us to hit that code path in those two examples? I'm not sure if I understand...
I think Johann is probably right about those use cases, but I'd like to make sure we aren't also ignoring something else that would matter in practice.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•