sunfish: Add best-effort `SunfishScannerFeatureWatcher`

For upcoming changes (b/391909810) to update the shelf home button
depending on whether Sunfish / Scanner UI can be shown, we would like a
way of observing that. Unlike the launcher button, we cannot simply
update the state when the launcher is shown, as the home button is
continuously shown.

Additionally, previous discussions in [1] mention that Sunfish and
Scanner UI _should_ dynamically update when the "can show UI" state of
the two features change. However, no such observer exists for these
features.

Observing the state which could affect the "can show UI" state of the
two features requires a lot of different observations, and it is
infeasible for all observers to implement these observations themselves.

Introduce a BEST-EFFORT watcher class, `SunfishScannerFeatureWatcher`,
which observes Sunfish and Scanner-related feature changes.
Unfortunately, as discussed in b/397301161, it is infeasible to watch
for all changes to the "show UI" states of these features, as Scanner's
checks are very hard to observe. Additionally, Sunfish's enterprise
policy is very difficult to observe (only in tests).

As this class is BEST-EFFORT, no direct tests have been written.
However, this CL introduces this watcher class to the launcher, so
existing tests which test Launcher behaviour
(`AppListControllerImplScannerEnabledTest`, `SunfishLauncherButtonTest`,
`ScannerMetricsTest`) should still pass with this change, despite some
of them using Sunfish's enterprise policy.

[1]: https://crrev.com/c/6284627/comment/c339a676_242bcda6/

Bug: b:391909810, b:397301161
Change-Id: I6a6a210087991e127f8760e990c135709afca2df
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6297203
Reviewed-by: Xiaoqian Dai <xdai@chromium.org>
Commit-Queue: Michael Cui <mlcui@google.com>
Cr-Commit-Position: refs/heads/main@{#1426892}
10 files changed
tree: 6716ae180021ce456903499b4ec8794d47f966a4
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .git-blame-ignore-revs
  53. .gitallowed
  54. .gitattributes
  55. .gitignore
  56. .gitmodules
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. CPPLINT.cfg
  68. CRYPTO_OWNERS
  69. DEPS
  70. DIR_METADATA
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. WATCHLISTS
README.md

Logo Chromium

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.