commit | 05c357a82f620a1c6e8bb3500bee76f14b086e99 | [log] [tgz] |
---|---|---|
author | Tom Burgin <bur@google.com> | Thu Mar 07 19:41:28 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Mar 07 19:41:28 2024 |
tree | e4e62b8ff206f052ac534c5e3cb48be566eecb7f | |
parent | b5d55696906e7521988c4ebc878a55872dcc01a8 [diff] |
immersive fullscreen: fix infobar missing clicks When the toolbar is hidden and the infobar is present, the overlay window is placed in an unexpected location causing clicks to be missed. After the remote cocoa immersive controller hides the overlay window, the Views controller (responding to a browser layout) changes the origin of the overlay window. We really only want the views controller to change the size, not the origin. This CL stops Views from driving the overlay window movement, allowing the remote cocoa immersive controller to move the window as expected. (cherry picked from commit 1cdaec6bbd3c0de62c1c9a3d3156feffbd3ba6b7) Bug: 326895880 Change-Id: I1a4c20a31070a51b41f56bac0fa370ef8329310b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5329026 Auto-Submit: Tom Burgin <bur@google.com> Reviewed-by: Leonard Grey <lgrey@chromium.org> Commit-Queue: Avi Drissman <avi@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1266037} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5352711 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6312@{#454} Cr-Branched-From: 6711dcdae48edaf98cbc6964f90fac85b7d9986e-refs/heads/main@{#1262506}
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.