Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CR134] Investigate impact of upstream removal of kReduceCookieIPCs #43918

Open
emerick opened this issue Feb 12, 2025 · 0 comments
Open

[CR134] Investigate impact of upstream removal of kReduceCookieIPCs #43918

emerick opened this issue Feb 12, 2025 · 0 comments
Assignees
Labels
Chromium/Followup Followup work logged during Chromium rebase dev-concern feature/cookies

Comments

@emerick
Copy link
Contributor

emerick commented Feb 12, 2025

Description

Now that kReduceCookieIPCs has been fully removed upstream, we should investigate if we need a better approach to handling that in light of ephemeral storage. We previously disabled kReduceCookieIPCs since we can switch the cookie storage backend at runtime and thus can't use reduced IPCs when accessing cookies. We currently have an override in place in chromium_src/third_party/blink/renderer/core/loader/cookie_jar.cc to deal with the loss of this flag, but we should investigate if it can be improved.

cc: @goodov

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Chromium/Followup Followup work logged during Chromium rebase dev-concern feature/cookies
Projects
None yet
Development

No branches or pull requests

2 participants