Reland "Fix context menu not dismissing when window moves with Win+Shift+Arrow"

This is a reland of commit 14045a2f04d9836ea9bd39477ffcdd96f374747b

This contains the original change, plus a fix for a crash that occurred
on Mac when invoking a menu while in immersive fullscreen.

A similar change commit c08a424435edeb00c5a539a6ae38f380adc56548
attempted to fix this issue, but isn't a complete fix. It will be
reverted once this CL lands. It attempts to listen to the key press
events, but Win+Shift+Arrow is an OS special key combination which is
eaten by the OS. This means the application never receives the key down
for arrow when Win and Shift are already pressed. So the other CL is
relying on the key up event. If the user releases Win or Shift keys
before releasing the arrow key, then the context menu is not dismissed
even though the browser window moves. Additionally, it doesn't handle up
and down keys, it doesn't handle if the window is moved with Win+Arrow
(no shift), and on single monitor displays, Win+Shift+Arrow does not
move the browser window, but the other CL still closes the context menu.

Using browser window move to dismiss the menu matches the behavior of
existing UI like Datalist dropdown and select dropdown, which dismiss
themselves when the browser window moves.

Original change's description:
> Fix context menu not dismissing when window moves with Win+Shift+Arrow
>
> The existing Destroying and ShowStateChanged callbacks, that
> MenuController uses to cancel currently showing menus, don't handle the
> case where the user moves the browser window using the keyboard shortcut
> Win+Shift+Arrow. Adding a callback for BoundsChanged to cancel current
> menus will handle the scenario where the user moves the browser window
> with the keyboard.
>
> Bug: 394634481
> Change-Id: I8fcceb209dbd376eda8a683525dcfb891d364a40
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6244522
> Reviewed-by: Dana Fried <dfried@chromium.org>
> Commit-Queue: Brad Peters <brpeters@microsoft.com>
> Reviewed-by: Alison Gale <agale@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1427428}

Bug: 394634481
Change-Id: If1ef4efb3a6d37be121d57a098daa4a2800c3348
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6474359
Reviewed-by: Dana Fried <dfried@chromium.org>
Commit-Queue: Brad Peters <brpeters@microsoft.com>
Reviewed-by: Liang Zhao <lzhao@microsoft.com>
Reviewed-by: Alison Gale <agale@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1458197}
6 files changed
tree: acfe14b2e056d7a4abf11ae669d1c1fece8a68b7
  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.