Google Git
Sign in
chromium / chromium / src / 98b5c3eceaf964bf01da3c6be18fa6608d17a30c
commit98b5c3eceaf964bf01da3c6be18fa6608d17a30c[log] [tgz]
authorYuwei Huang <yuweih@chromium.org>Fri Aug 29 03:02:42 2025
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Aug 29 03:02:42 2025
treea3bfa93588df4d76e159c6af61f9bbda9c3609a9
parente8f869920469f0096cf5a5ce0e6505ab18014cde [diff]
[crd host][wayland] Set monitor layout

This CL updates GnomeDesktopResizer so that the monitor layout
configured via the VideoLayout protobuf will be applied to Mutter's
virtual monitor.

One issue I've found is that, Mutter has a tendency to change the layout
back to horizontal start-aligned whenever a monitor is resized via
PipeWire. To allow the layout to stick, we calculate the layout info
whenever the VideoLayout is received, or before a monitor is resized, if
it is not yet set, then we relayout with the layout info right before we
call ApplyMonitorsConfig.

Due to `preferred_monitors_config_` and `preferred_layout_`, the host's
display config will be entirely controlled by the client, meaning if the
user tries to change the display config via the settings app, it will be
immediately reverted by GnomeDesktopResizer. In the next CL, I'll look
into relaxing this by clearing these fields with a timer, hopefully
after the display config has stabilized. This is required for
implementing RestoreResolution().

Bug: 432217140
Change-Id: I6ef899ef1afee45db6e5f2ad0cedccb8e04652fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6893890
Reviewed-by: Lambros Lambrou <lambroslambrou@chromium.org>
Commit-Queue: Yuwei Huang <yuweih@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1508150}
2 files changed
tree: a3bfa93588df4d76e159c6af61f9bbda9c3609a9
  1. .gemini/
  2. .github/
  3. agents/
  4. android_webview/
  5. apps/
  6. ash/
  7. base/
  8. build/
  9. build_overrides/
  10. buildtools/
  11. cc/
  12. chrome/
  13. chromecast/
  14. chromeos/
  15. codelabs/
  16. components/
  17. content/
  18. crypto/
  19. dbus/
  20. device/
  21. docs/
  22. extensions/
  23. fuchsia_web/
  24. gin/
  25. google_apis/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. media/
  32. mojo/
  33. net/
  34. pdf/
  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. clusterfuzz-data
  52. internal
  53. ios_internal
  54. signing_keys
  55. v8
  56. .clang-format
  57. .clang-tidy
  58. .clangd
  59. .cursorignore
  60. .geminiignore
  61. .git-blame-ignore-revs
  62. .gitallowed
  63. .gitattributes
  64. .gitignore
  65. .gitmodules
  66. .gn
  67. .mailmap
  68. .rustfmt.toml
  69. .vpython3
  70. .yapfignore
  71. ATL_OWNERS
  72. AUTHORS
  73. BUILD.gn
  74. CODE_OF_CONDUCT.md
  75. codereview.settings
  76. CPPLINT.cfg
  77. CRYPTO_OWNERS
  78. DEPS
  79. DIR_METADATA
  80. LICENSE
  81. LICENSE.chromium_os
  82. OWNERS
  83. PRESUBMIT.py
  84. PRESUBMIT_test.py
  85. PRESUBMIT_test_mocks.py
  86. README.md
  87. SECURITY_OWNERS
  88. 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.