Files
Emma Zuehlcke 2213eda366 Bug 2058143 - Part 8: Remove the cookie banner handling implementation. r=necko-reviewers,ipc-reviewers,frontend-codestyle-reviewers,chutten,kershaw,mossop,timhuang
Deletes toolkit/components/cookiebanners and everything that reached into it:
the static and runtime prefs, the JSWindowActor registration, the
nsILoadInfo.hasInjectedCookieForCookieBannerHandling plumbing and its IPC
serialization, the Glean and Legacy Telemetry registrations, the Nimbus
feature, and the shipped cookie-banner-rules-list Remote Settings dump.

Notes for reviewers:

- Removing the cookiebanners pref group from modules/libpref/moz.build and the
  StaticPrefList.yaml block must happen together; a mismatch fails at build
  time rather than lint time.
- Deleting the local dump does not decommission the main/cookie-banner-rules-list
  Remote Settings collection. ESR and older clients still sync it live, so the
  server-side collection needs to outlive them and be retired separately.
- docs/overview/gecko.md used nsCookieBannerService purely as its worked
  example of XPCOM component instantiation; the diagram is kept with a service
  that still exists.
- Recorded perf pages will now show cookie banners, since hooks_recording.py no
  longer sets the dismissal prefs. Worth a follow-up if that shifts baselines.

Differential Revision: https://phabricator.services.mozilla.com/D314673
2026-08-05 10:10:54 +00:00
..