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}
18 files changed
tree: 707f003eb72a72123996514b55de59fbac9e3a1d
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. google_update/
  24. gpu/
  25. headless/
  26. infra/
  27. ios/
  28. ipc/
  29. media/
  30. mojo/
  31. native_client_sdk/
  32. net/
  33. pdf/
  34. ppapi/
  35. printing/
  36. remoting/
  37. rlz/
  38. sandbox/
  39. services/
  40. skia/
  41. sql/
  42. storage/
  43. styleguide/
  44. testing/
  45. third_party/
  46. tools/
  47. ui/
  48. url/
  49. webkit/
  50. .clang-format
  51. .clang-tidy
  52. .clangd
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitallowed
  56. .gitattributes
  57. .gitignore
  58. .gitmodules
  59. .gn
  60. .mailmap
  61. .rustfmt.toml
  62. .vpython3
  63. .yapfignore
  64. ATL_OWNERS
  65. AUTHORS
  66. BUILD.gn
  67. CODE_OF_CONDUCT.md
  68. codereview.settings
  69. CPPLINT.cfg
  70. CRYPTO_OWNERS
  71. DEPS
  72. DIR_METADATA
  73. LICENSE
  74. LICENSE.chromium_os
  75. OWNERS
  76. PRESUBMIT.py
  77. PRESUBMIT_test.py
  78. PRESUBMIT_test_mocks.py
  79. README.md
  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.