commit | e090569871f2738e3c560e508bb756d545f57a4f | [log] [tgz] |
---|---|---|
author | Victor Hugo Vianna Silva <victorvianna@google.com> | Fri Feb 02 18:13:40 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Feb 02 18:13:40 2024 |
tree | 08a613cceb14df10df216ff858ceeb9c43ecee2b | |
parent | 41d13d38b34cbc24be3c2bf94b260291beeea0de [diff] |
Remove sync suppression logic while local UPM migration is pending Behavior changes are behind flag. Partial revert of crrev.com/c/5088712. The suppression logic will have to be implemented differently, remove for now. After this CL it is possible to enable password sync while the migration is pending, but in *transport* mode, without any upload of existing data. This setup of overriding the SyncMode to kTransportOnly in the controller can potentially be reused on Desktop in the future, if we decide to always run passwords in transport mode ahead of fully deprecating sync-the-feature. So gate it behind a new kEnablePasswordsAccountStorageForSyncingUsers toggle. This toggle will also be consumed by IsOptedInForAccountStorage() in future CLs. Unrelated to that, also add a comment next to the usage of the corresponding flag for non-syncing users. Bug: 1509058 Change-Id: I70fe3497e46bb0f03611fa96844bc71eb6f3a300 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5262157 Auto-Submit: Victor Vianna <victorvianna@google.com> Commit-Queue: Victor Vianna <victorvianna@google.com> Commit-Queue: Vasilii Sukhanov <vasilii@chromium.org> Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org> Cr-Commit-Position: refs/heads/main@{#1255656}
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.