Window Placement: Prototype Fullscreen Capability Delegation - Part 2

This completes the prototype started in https://crrev.com/c/3575071

Support Fullscreen Capability Delegation when a flag is enabled:
  --enable-blink-features=CapabilityDelegationFullscreenRequest
Frames can delegate via messaging another frame on activation:
- w.postMessage(m, { targetOrigin: o, delegate: "fullscreen" });
Another frame can use the delegated capability on message receipt:
- window.onmessage = () => { e.requestFullscreen(); }

Activate a browser-side FullscreenRequestToken in:
- RFHI::PostMessageEvent for RemoteFrameHost's RouteMessageEvent
- new ReceivedDelegatedCapability for LocalFrameHost local messages

Focus windows that had delegation to request fullscreen, so:
- user can press [Esc] to exit fullscreen
- another focused window doesn't z-order above/below fullscreen

Add automated tests supporting feature flag and local/remote usage

(cherry picked from commit dbf43d9bce4a203ed01b1becb06f3f263fd9c4c3)

Bug: 1293083
Test: automated; Fullscreen Capability Delegation WAI with flag enabled
Change-Id: Ie46e627cd8df033016f16afbfda4075da81517b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3642842
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Commit-Queue: Mike Wasserman <msw@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1005525}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3658340
Auto-Submit: Mike Wasserman <msw@chromium.org>
Commit-Queue: Charlie Reis <creis@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5060@{#187}
Cr-Branched-From: b83393d0f4038aeaf67f970a024d8101df7348d1-refs/heads/main@{#1002911}
12 files changed
tree: bcaa0d91503e488e3fb482f9e0fc94ff9f7d1ace
  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. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia/
  22. fuchsia_webengine/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. media/
  32. mojo/
  33. native_client_sdk/
  34. net/
  35. pdf/
  36. ppapi/
  37. printing/
  38. remoting/
  39. rlz/
  40. sandbox/
  41. services/
  42. skia/
  43. sql/
  44. storage/
  45. styleguide/
  46. testing/
  47. third_party/
  48. tools/
  49. ui/
  50. url/
  51. weblayer/
  52. .clang-format
  53. .clang-tidy
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitattributes
  57. .gitignore
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  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.