commit | 21054d089975e150a1b6c5c5ab826cd7ee9c4ccc | [log] [tgz] |
---|---|---|
author | Antonio Gomes <tonikitoo@igalia.com> | Thu Apr 04 08:57:11 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 04 08:57:11 2024 |
tree | 2a29328852436fd9b5d01c9d9c28042cecada3f6 | |
parent | b7f2ffa3d916ef9355b949f094a7e745d12d5e17 [diff] |
[ozone/wayland] Standardize calls to gfx::ScaleToEnclosingRectIgnoringError() The predecessor CL [1] changed how gfx::ScaleToEnclosingRectIgnoringError() is called in both WaylandWindow::RequestState() and WaylandPopup::OnInitialize(), when setting the value of PlatformWindowDelegate::State::size_px : Now, instead of passing PlatformWindowDelegate::State::bounds_dip rect as parameter to gfx::ScaleToEnclosingRectIgnoringError(), only PlatformWindowDelegate::State::bounds_dip's size is used (see comment message of [1] for details). This is follow up CL that also applies the same logic in the newly added [2] WaylandBubble::OnInitialize() method. In practice, it won't change any behavior, since WaylandWindow::RequestState() is usually called after WaylandBubble::OnInitialize(), and `size_px` value is "fixed" there. Nonetheless, it is good to have consistency. [1] https://crrev.com/c/5384752 [2] https://crrev.com/c/5301619 R=msisov@igalia.com Bug: 40876438 Change-Id: I253c6872a12ca63e258dfd064c1767d8983f2eb0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5419514 Reviewed-by: Maksim Sisov <msisov@igalia.com> Commit-Queue: Antonio Gomes <tonikitoo@igalia.com> Cr-Commit-Position: refs/heads/main@{#1282370}
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.