Expose trusted vault opt-in entry point on Android Chrome settings This is an analogous of crrev.com/c/2859026 for Android. All considerations about when the entry point is shown/hidden also apply here. Strings are not final and the entry point does nothing when clicked for the moment. Implementation: crbug.com/1202088#c5 Mock (sorry, Googlers only): https://docs.google.com/presentation/d/1FhpO2px56jU0YIrByqNysSdLcZ2s9CkIy-J_QS3s1PY/edit#slide=id.g97310fee6c_1_20 Bug: 1202088 Change-Id: I67453423b4275fd210ca822d346797ddb084cc28 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2922251 Commit-Queue: Victor Vianna <victorvianna@google.com> Reviewed-by: Marc Treib <treib@chromium.org> Reviewed-by: Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#887718}
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.