commit | 1ef7bd27840d7fcd0940d68416e736cf9df3d951 | [log] [tgz] |
---|---|---|
author | amarjotgill <amarjotgill@google.com> | Mon Feb 03 15:32:54 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Feb 03 15:32:54 2025 |
tree | f4c4dea94520be3f38fc0d442a908e5f695c19a8 | |
parent | 7284c0e088f223c4e4069f7e632e26be783916b0 [diff] |
Revert "[OBC] Exclude Aliasing Cookies in FilterCookiesWithOptions()" This reverts commit fcdf811e2ffd91bff30b42d34e5240781d747dcb. Reason for revert: Has been decided that a simple and more efficient implementation will work better discussed here https://docs.google.com/document/d/1Br7i5RzY8rqKNsdzICGlc8IGWzZj0cqQyactiaFf95g/edit?pli=1&resourcekey=0-wRkDQxnwkkF7IR8-Nnh1Gw&tab=t.0#heading=h.y7rl2pm4q74v Original change's description: > [OBC] Exclude Aliasing Cookies in FilterCookiesWithOptions() > > Introducing a new cookie exclusion type EXCLUDE_ALIASING > when CookieScopeSemantics is LEGACY a cookie who is aliasing > another cookie and is not the most recently created cookie > will be marked with this new exclusion type. > > Bug: 378827534 > Change-Id: I01654bcff01e9aeff23b870d0b45c69883405dcb > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6071023 > Auto-Submit: Amarjot Gill <amarjotgill@chromium.org> > Reviewed-by: Steven Bingler <bingler@chromium.org> > Commit-Queue: Amarjot Gill <amarjotgill@chromium.org> > Reviewed-by: Dylan Cutler <dylancutler@google.com> > Cr-Commit-Position: refs/heads/main@{#1396751} Bug: 378827534 Change-Id: I8a59702769e57a71f0c2765a664ac229e26cb397 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6221378 Reviewed-by: Steven Bingler <bingler@chromium.org> Commit-Queue: Amarjot Gill <amarjotgill@chromium.org> Cr-Commit-Position: refs/heads/main@{#1414920}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.