Google Git
Sign in
chromium / chromium / src / 226e5f11e56e8d24a3eea33402395ee7e5a6f2d8
commit226e5f11e56e8d24a3eea33402395ee7e5a6f2d8[log] [tgz]
authorNick Diego Yamane <nickdiego@igalia.com>Wed Sep 11 00:57:49 2024
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Sep 11 00:57:49 2024
treeb311d84d468bdc05476e49cc2dcb0118bb5fbf66
parentb812a96d623e7de211ddfd06c3d502e8f2b478bc [diff]
wayland ui scaling: use LinuxUi scaling info in ozone/wayland

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 patches ozone/wayland so that it now retrieves and watches for font
scaling updates to notify wayland windows about it. This basically adds
the plumbing code, the actual scaling logic changes will be added in the
upcoming CL.

R=orko@igalia.com, thomasanderson

Bug: 40856031, 41486578
Change-Id: I2175698eb158106141f0e7c7b3aac85240a29664
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5836739
Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Commit-Queue: Nick Yamane <nickdiego@igalia.com>
Reviewed-by: Orko Garai <orko@igalia.com>
Cr-Commit-Position: refs/heads/main@{#1353695}
4 files changed
tree: b311d84d468bdc05476e49cc2dcb0118bb5fbf66
  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. clank
  51. internal
  52. ios_internal
  53. native_client
  54. signing_keys
  55. v8
  56. .clang-format
  57. .clang-tidy
  58. .clangd
  59. .eslintrc.js
  60. .git-blame-ignore-revs
  61. .gitallowed
  62. .gitattributes
  63. .gitignore
  64. .gitmodules
  65. .gn
  66. .mailmap
  67. .rustfmt.toml
  68. .vpython3
  69. .yapfignore
  70. ATL_OWNERS
  71. AUTHORS
  72. BUILD.gn
  73. CODE_OF_CONDUCT.md
  74. codereview.settings
  75. CPPLINT.cfg
  76. CRYPTO_OWNERS
  77. DEPS
  78. DIR_METADATA
  79. LICENSE
  80. LICENSE.chromium_os
  81. OWNERS
  82. PRESUBMIT.py
  83. PRESUBMIT_test.py
  84. PRESUBMIT_test_mocks.py
  85. README.md
  86. 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.