scanner: Abstract out disclaimer prefs logic into separate file This should be a pure refactor with no behavioural changes. This hides the implementation detail of what prefs are used to show / hide the disclaimer. This currently is a trivial wrapper around getting a boolean from a pref, but future CLs will extend this further to support for different entrypoints and reminder disclaimers. Bug: b:383437797 Change-Id: I6a6a2100edf7a390e8170d83176160ac2cf8fb05 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6356186 Reviewed-by: Sammie Quon <sammiequon@chromium.org> Commit-Queue: Michael Cui <mlcui@google.com> Cr-Commit-Position: refs/heads/main@{#1433353}
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.