[win] Change ScreenWin public static methods to virtual

CL http://crrev.com/c/6332686 introduced an alternate headless aware
ScreenWin implementation. However, since all ScreenWin public methods
are static, we'll have to resort to some ugly proxy classes in order to
orchestrate access to the public ScreenWin functionality.

A cleaner, albeit somewhat intrusive, solution is to change ScreenWin
public interface methods to be all virtual. This way normal and headless
aware functionality will be seamlessly available using the standard
mechanism of calling virtual methods via the static instance getter.

One issue with this approach is that many tests call ScreenWin public
methods before ScreenWin instance is created. Static ScreenWin methods
return a generic response in this case, however, virtual ScreenWin
methods need an instance to be invoked. Instead of modifying the tests
the ScreenWin instance getter lazily creates a fallback ScreenWin
instance and uses it to serve generic responses until the real ScreenWin
is created or the test terminates.

Most of the files in this CL are ScreenWin public method call sites that
are mechanically updated with
s/display::win::ScreenWin::/display::win::GetScreenWin()->/.

The meaningful changes are in //ui/display/win/screen_win*.

Change-Id: Iafbc6323be41639e4565a4b0c63b1202e8279be9
AX-Relnotes: n/a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6419936
Reviewed-by: Robert Liao <robliao@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Peter Kvitek <kvitekp@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1443607}
44 files changed
tree: b0cc27e5b7ef3ce8b931aac65f0748029fb2814c
  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.