Relocate password leak toggle from safe browsing page to privacy page This change removes the password leak detection toggle from the standard protection fragment and makes it it's own setting on the privacy page for Android. We are also removing the safebrowsing protection level dependency on the password leak toggle enable status so the now the user has free choice to select whether they want the password leak toggle enabled regardless of safe browsing status. We will also remove the enhanced protection bullet point about password leak detection since that is no longer accurate. Respective Desktop Implementation CLs: https://crrev.com/c/6000457 & https://crrev.com/c/5899277 Password Leak Detection Screenshots: Screenshot(Before):https://crbug.com/370770920#comment33 Screenshot(After):https://crbug.com/370770920#comment32 Enhanced Protection Screenshots: Screenshot(Before):https://crbug.com/370770920#comment34 Screenshot(AFter):https://crbug.com/370770920#comment35 Bug: 370770920 Change-Id: I7a84a82d89944d5f11914a27dd04ccdd477feccf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6158427 Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Reviewed-by: Theresa Sullivan <twellington@chromium.org> Reviewed-by: Xinghui Lu <xinghuilu@chromium.org> Commit-Queue: Awad Osman <awado@google.com> Cr-Commit-Position: refs/heads/main@{#1404385}
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.