Closed
Bug 1799341
Opened 3 years ago
Closed 3 years ago
Only run cookie banner handling mechanism for browser tabs
Categories
(Core :: Privacy: Anti-Tracking, task)
Core
Privacy: Anti-Tracking
Tracking
()
RESOLVED
FIXED
108 Branch
| Tracking | Status | |
|---|---|---|
| firefox108 | --- | fixed |
People
(Reporter: emz, Assigned: emz)
References
Details
Attachments
(1 file)
We can optimize our cookie clicking and injection code by restricting it to BrowsingContexts that are in the "browsers" group. This will prevent the mechanisms from running in browsers that are not related to tabs.
In the cookie injector we can check via browsingContext->GetMessageManagerGroup().EqualsLiteral("browsers"). For the JSWindowActor registration of CookieBannerParent/Child we can use: messageManagerGroups: ["browsers"].
| Assignee | ||
Comment 1•3 years ago
|
||
Updated•3 years ago
|
Assignee: nobody → pbz
Status: NEW → ASSIGNED
Pushed by pzuhlcke@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1ade1488cd3d
Restrict CookieBanner JSWindowActor and nsCookieInjector to message manager group browser. r=timhuang
Comment 3•3 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox108:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 108 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•