| commit | 3d49d76b5f024554b96872d83cef11a49ac51283 | [log] [tgz] |
|---|---|---|
| author | Ankush Singh <ankushkush@google.com> | Fri May 09 15:56:54 2025 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 09 15:56:54 2025 |
| tree | 641c165dfc32efbd4fb0f83aa8c961cbd7ad8859 | |
| parent | 5b0f8ef0e3ca94af455306b99bf06196e37c9b47 [diff] |
[prefs] Store user_selected_types in a pref in local store This CL tackles a bug in the newly introduced code for always syncing priority prefs: Priority prefs not marked as always syncing do not return the account value before sync service is initialized, i.e. before DualLayerUserPrefStore::OnSyncServiceInitialized() is called. This is because the user selected sync types are not yet known and we avoid returning priority pref values if "preference" is not selected by the user for sync. This bug _might_ affect services which request a priority pref before this point. With this CL, the user selected types are preserved from the previous run in a local-only preference. This allows deciding whether to return the account priority pref value right away. Any change to the user selected types will get informed when DualLayerUserPrefStore::OnSyncServiceInitialized() is called. Bug: 412602018 Change-Id: I68e9c9b82b13d6a5357b0cca10c5454b750f47be Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6519735 Commit-Queue: Ankush Singh <ankushkush@google.com> Reviewed-by: Marc Treib <treib@chromium.org> Auto-Submit: Ankush Singh <ankushkush@google.com> Cr-Commit-Position: refs/heads/main@{#1458143}
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.