commit | 756e64489c84c22998470beddb1facab5e78e1fa | [log] [tgz] |
---|---|---|
author | Nick Diego Yamane <nickdiego@igalia.com> | Tue Sep 24 16:38:16 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Sep 24 16:38:16 2024 |
tree | 707f003eb72a72123996514b55de59fbac9e3a1d | |
parent | 74a5382ac8bb0b825627fdfc3a35ccede9187d9f [diff] |
wayland ui scaling: scale chrome UI upon LinuxUi's font scale changes This is part of the set of changes required to support Desktop Environment's "Large Text" accessibility setting in Chromium's Wayland backend. It actually can also be triggered by other system tools, such as, Gnome Tweaks app as well as gsettings command line tool in Gnome ecosystem. Design doc: https://docs.google.com/document/d/16kwPm_S0dmxe4kSgKY0_PA7aFvkFcftx6AMzNqT8Nfg This implements the first part of chrome UI scaling upon LinuxUi's font scale changes. To do so, it adds a ui_scale field to PlatformWindowDelegate::State struct and fires OnBoundsChanged callback when font scale change is triggered by GtkUi. The bounds change consists of a ui scale update but keeping the DIP window size unchanged, which will result in a UI content resize and relayout. The feature is behind the newly added `WaylandUiScale` feature flag, disabled by default. At this point the follow command line flags must be used to enable the WIP feature implemented by this patch series: `gtk-version=4 --enable-features=WaylandPerSurfaceScale,WaylandUiScale` Upcoming CLs will implement the remaining required functionality to fully support this new UI scaling feature. Bug: 40856031, 41486578 Change-Id: Ie58d1f0fd4ec30795bf84f12f02028e4c7951287 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5852358 Reviewed-by: Eliot Courtney <edcourtney@chromium.org> Commit-Queue: Nick Yamane <nickdiego@igalia.com> Reviewed-by: Kramer Ge <fangzhoug@chromium.org> Cr-Commit-Position: refs/heads/main@{#1359412}
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.