| commit | 18966bc75cf721c39fd304fdceff1e40b80c6893 | [log] [tgz] |
|---|---|---|
| author | Wenyu Fu <wenyufu@chromium.org> | Thu Nov 14 03:37:15 2024 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Nov 14 03:37:15 2024 |
| tree | 486a1db6d997405a8a97a5d68f5d5a4ea8afcb86 | |
| parent | 821b5fda458f4dc3058bcc64145bffeb43ae70cc [diff] |
[E2E] Read system bar insets for edge to edge Before this CL, EdgeToEdgeControllerImpl observe insets changes for navigation bar and status bar. On some OEM (e.g. Redmi), their split screen window has a captionBar insets which is not handled in edge to edge, and part of the Chrome UI will draw under those insets, make Chrome broken. This CL makes EdgeToEdgeController reads all systemBar insets (captionBar + statusBar + navigationBar) to fix the issue. Verified on device that doesn't use captionBars, there's no impact observed. -- Risks: this new logic might be broken if we have captionBar insets coming from the bottom. TBD if any OEM has this behavior. -- Demo: Redmi: https://screencast.googleplex.com/cast/NTE2MzgyMDY4NjI0NTg4OHxiMjIyNzAwOC1mYw Pixel 5a: https://screencast.googleplex.com/cast/NTU2ODI0MTMzMzE3NDI3MnxjZmNiOGM4My01OQ Bug: 377620837 Change-Id: Ib6c0bf1bd86d4c41e1c6db0d84fa44e0d7d66ce8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6020232 Reviewed-by: Charles Hager <clhager@google.com> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Commit-Queue: Wenyu Fu <wenyufu@chromium.org> Cr-Commit-Position: refs/heads/main@{#1382786}
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.