Reland "Track picture-in-picture occlusion for extension install dialog"

This is a reland of commit 9239872ef90b5994cf74135a259feacf2cdda221

The original CL failed because the extension install dialog, on Mac-12,
appears to always want to be centered.

The fix is to switch the order when forcing the widgets to overlap.
Now, when forcing an overlap, the bounds are set for the
Picture-in-Picture widget, instead of the extension install dialog
widget.

Original change's description:
> Track picture-in-picture occlusion for extension install dialog
>
> This change updates the extension install dialog to:
>   * Prevent user input when occluded by a picture-in-picture window
>   * Maintain input protection for a short period after the
>     picture-in-picture window is closed, through the use of the input
>     protector
>
> Bug: 40067402
> Change-Id: I0e0574688bb3c3c86bcc611b64e16ef624fff2e9
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6735194
> Commit-Queue: Benjamin Keen <bkeen@google.com>
> Reviewed-by: Devlin Cronin <rdevlin.cronin@chromium.org>
> Reviewed-by: Tommy Steimel <steimel@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1490961}

Bug: 40067402
Change-Id: Iad65987cb439e2a5795e9e25524bbc97cc43a614
Include-Ci-Only-Tests: chromium.mac:Mac12 Tests|browser_tests
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6777898
Commit-Queue: Benjamin Keen <bkeen@google.com>
Reviewed-by: Devlin Cronin <rdevlin.cronin@chromium.org>
Reviewed-by: Tommy Steimel <steimel@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491606}
5 files changed
tree: 50dab8d570389f070e9d46ee3a0afb0c41d2da28
  1. .github/
  2. agents/
  3. android_webview/
  4. apps/
  5. ash/
  6. base/
  7. build/
  8. build_overrides/
  9. buildtools/
  10. cc/
  11. chrome/
  12. chromecast/
  13. chromeos/
  14. codelabs/
  15. components/
  16. content/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia_web/
  23. gin/
  24. google_apis/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. net/
  33. pdf/
  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. .cursorignore
  53. .git-blame-ignore-revs
  54. .gitallowed
  55. .gitattributes
  56. .gitignore
  57. .gitmodules
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython3
  62. .yapfignore
  63. ATL_OWNERS
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. CPPLINT.cfg
  69. CRYPTO_OWNERS
  70. DEPS
  71. DIR_METADATA
  72. LICENSE
  73. LICENSE.chromium_os
  74. OWNERS
  75. PRESUBMIT.py
  76. PRESUBMIT_test.py
  77. PRESUBMIT_test_mocks.py
  78. README.md
  79. SECURITY_OWNERS
  80. 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.