Investigate cookie jar sizes in a state partitioned world
Categories
(Core :: Networking: Cookies, task, P2)
Tracking
()
People
(Reporter: edgul, Unassigned)
References
Details
(Whiteboard: [necko-triaged])
As mentioned in Bug 1828942 comment 4, the first step will be adding telemetry, handled by Necko. That telemetry will be added to that bug and the broader investigation will continue in this bug.
+++ This bug was initially created as a clone of Bug #1828942 +++
We expect that since we shipped Total Cookie Protection, partitioning cookies, the amount of cookies set in profiles has increased. We should quantify this using telemetry.
If we store many more cookies (per top level site) with TCP there is the risk that recently used cookies get purged too early leading to data loss and an overall bad user experience when browsing.
This topic also came up at TPAC 2022 where folks from Safari/Webkit mentioned that they had concerns over partitioning 3rd-party by default because of potentially larger cookie jars.
Relevant prefs:
network.cookie.maxNumber
network.cookie.maxPerHost
Description
•