Closed
Bug 1801074
Opened 2 years ago
Closed 2 years ago
Don't run cookie banner clicking by default in sub-frames
Categories
(Core :: Privacy: Anti-Tracking, task, P2)
Core
Privacy: Anti-Tracking
Tracking
()
RESOLVED
FIXED
109 Branch
| Tracking | Status | |
|---|---|---|
| firefox109 | --- | fixed |
People
(Reporter: emz, Assigned: emz)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
We mostly handle cookie banners for top level sites so we can skip running the cookie banner handling code by default in sub-frames. Adding a boolean flag in our rules means we can enable it for specific sites / CMPs.
nsICookieInjector already only injects cookies for top level loads.
CookieBannerChild can check the rule for the flag and abort for sub-frames if it's false.
|
Assignee | |
Comment 1•2 years ago
|
||
|
||
Updated•2 years ago
|
Assignee: nobody → pbz
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 2•2 years ago
|
||
Depends on D162324
Pushed by pzuhlcke@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/e59d7eb60ad2
Add runContext nsIClickRule flag. r=timhuang
https://hg.mozilla.org/integration/autoland/rev/c6767513c4f5
Update tests for runContext nsIClickRule flag. r=timhuang
|
||
Comment 4•2 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/e59d7eb60ad2
https://hg.mozilla.org/mozilla-central/rev/c6767513c4f5
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox109:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 109 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•