Closed Bug 1801084 Opened 3 years ago Closed 3 years ago

Dispatch cookiebannerhandled for banners handled via cookie injection

Categories

(Core :: Privacy: Anti-Tracking, task, P3)

task

Tracking

()

RESOLVED DUPLICATE of bug 1800102

People

(Reporter: emz, Unassigned)

References

Details

Currently only CookieBannerChild dispatches cookiebannerhandled when it closes a banner. We should also do it for the cookie injection case.

The cookie injector should only send this signal to the service if it sets a cookie that has previously not been set to avoid duplicate notifications for sites where we have already handled the banner. This is a bit tricky to determine since we usually only set session cookies. We might have to add a persistent store to keep track of which sites we handled via cookie injection.
The other difficulty is dispatching the event at the right time. The injector code runs before the HTTP connection is even established. How can we tie the event to the content window / WindowContext? We might need to cache a flag in the load-info and dispatch it once the content window is created and discard it otherwise.

Status: NEW → RESOLVED
Closed: 3 years ago
Duplicate of bug: 1800102
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.