[Gardener] Revert "Privacy guide: Show history sync card for signed-in users" This reverts commit 4a271d33212e1e47c66b41c8a9b3a649cad27dbf. Reason for revert: Fails on Win10 builds. See failures: https://ci.chromium.org/ui/p/chromium/builders/ci/Win10%20Tests%20x64 Original change's description: > Privacy guide: Show history sync card for signed-in users > > This CL does the following: > 1. Sets replaceSyncPromosWithSignInPromos in load time data for ChromeOS as well, to allow the tests to pass -> the value will always be false and the tests should already handle that. > 2. Shows the history sync card for signed in users if > replaceSyncPromosWithSignInPromos is set. > 3. Sets the initial toggle value of history sync toggle in the privacy > guide to only be decided by typedUrlsSynced bit. > > Bug: 445673760 > Change-Id: I642b2832ff81db6bbb31d2e5041ca8395c4ba8c8 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6960193 > Commit-Queue: Marc Treib <treib@chromium.org> > Commit-Queue: Ankush Singh <ankushkush@google.com> > Auto-Submit: Ankush Singh <ankushkush@google.com> > Reviewed-by: Marc Treib <treib@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1527444} Bug: 445673760 No-Presubmit: true No-Tree-Checks: true No-Try: true Change-Id: I7fb6dcb20f52f12f0208e4b595c74b06f0eaaa57 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7027056 Auto-Submit: Sana Akbani <sanaakbani@google.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Reviewed-by: Darryl James <dljames@chromium.org> Commit-Queue: Darryl James <dljames@chromium.org> Cr-Commit-Position: refs/heads/main@{#1527671}
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.