[CVV Storage] Adding syncing of Local changes to the Chrome sync servers Whenever any local storage change occurs for the Server cvc, we will trigger a sync of the same to the Chrome sync servers. DD- go/pay-autofill-cvv-storage-chrome AutofillWebDataServiceObserverOnDBSequence will be implemented by the sync bridge. Low-Coverage-Reason: This component will be tested when Bug: 1458044 Change-Id: Iec72aeb18c4f02fbe182f10a170681645dad635e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4766968 Reviewed-by: Alexander Tekle <alexandertekle@google.com> Reviewed-by: Marc Treib <treib@chromium.org> Reviewed-by: Siyu An <siyua@chromium.org> Commit-Queue: Vipul Koul <koulvipul@google.com> Reviewed-by: Dominic Battre <battre@chromium.org> Cr-Commit-Position: refs/heads/main@{#1188575}
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.