[ozone/wayland] Implement PointerLock

In Wayland, it is not possible that the client controls the Pointer
(cursor) position. The existing cross-platform Chrome implementation
for "Mouse Lock" rely on this premise, which is not in place.

  WaylandWindow::MoveCursorTo(Point)

Wayland, then, provides two extensions supported by major Desktop
compositors (eg Gnome) and Exo, in order to fill the gap:
zwp_pointer_contraints and zwp_relative_pointer_manager.

This CL implements both, and provide the Pointer Lock functionality
to both Chrome/Wayland desktop and Lacros.

Here is flow with the current CL when a pointer lock is requested
by the HTML content:

   Renderer
      |
      | (mojo)
      |
   Browser
      |------> RenderWidgetHostViewEventHandler::LockMouse()
                              |
                              | (asks)
                              |
                 WindowTreeHost::SupportsMouseLock()
                          /               \
                         / yes             \ no
                        /                   \
          WTH::LockMouse()                   \
                  |                         (Current code path..)
                  |
  WaylandExtension::LockPointer(true)
                  |
                  |
  WaylandTopLevelWindow::LockPointer(true)
                  |
                  | enables
                  |
  ZwpPointerConstraints
                  +
                  ZwpRelativePointerManager

BUG=1208843
TEST=https://mdn.github.io/dom-examples/pointer-lock/

Change-Id: Ia9ee6b896b23f2ee8ba502c43fb09b16c515195a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2983858
Commit-Queue: Antonio Gomes <tonikitoo@igalia.com>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Maksim Sisov <msisov@igalia.com>
Cr-Commit-Position: refs/heads/master@{#898696}
13 files changed
tree: 20ede3d2fd6dc723b4c1f44daa5e865927ae84a4
  1. .clang-format
  2. .clang-tidy
  3. .eslintrc.js
  4. .git-blame-ignore-revs
  5. .gitattributes
  6. .gitignore
  7. .gn
  8. .mailmap
  9. .vpython
  10. .vpython3
  11. .yapfignore
  12. AUTHORS
  13. BUILD.gn
  14. CODE_OF_CONDUCT.md
  15. DEPS
  16. DIR_METADATA
  17. ENG_REVIEW_OWNERS
  18. LICENSE
  19. LICENSE.chromium_os
  20. OWNERS
  21. PRESUBMIT.py
  22. PRESUBMIT_test.py
  23. PRESUBMIT_test_mocks.py
  24. README.md
  25. WATCHLISTS
  26. android_webview/
  27. apps/
  28. ash/
  29. base/
  30. build/
  31. build_overrides/
  32. buildtools/
  33. cc/
  34. chrome/
  35. chromecast/
  36. chromeos/
  37. cloud_print/
  38. codelabs/
  39. codereview.settings
  40. components/
  41. content/
  42. courgette/
  43. crypto/
  44. dbus/
  45. device/
  46. docs/
  47. extensions/
  48. fuchsia/
  49. gin/
  50. google_apis/
  51. google_update/
  52. gpu/
  53. headless/
  54. infra/
  55. ios/
  56. ipc/
  57. jingle/
  58. media/
  59. mojo/
  60. native_client_sdk/
  61. net/
  62. pdf/
  63. ppapi/
  64. printing/
  65. remoting/
  66. rlz/
  67. sandbox/
  68. services/
  69. skia/
  70. sql/
  71. storage/
  72. styleguide/
  73. testing/
  74. third_party/
  75. tools/
  76. ui/
  77. url/
  78. weblayer/
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.