| commit | d0e6fa3b4a5ae3406c88bc94258f18b94279235b | [log] [tgz] |
|---|---|---|
| author | Nick Diego Yamane <nickdiego@igalia.com> | Thu Mar 27 00:21:44 2025 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Mar 27 00:21:44 2025 |
| tree | d81d583c55357ba6e8a506a91ec3d141ea9ae663 | |
| parent | 81b4d918ffc7916505ec3d9dbc62104b63093937 [diff] |
wayland: xdg-session-management: Add required UI/Views toolkit bits
Some platforms support session management assisted by the display
server. Such as, Linux/Wayland with the xdg-session-management protocol
extension. In this CL, the following components are added to a few
different layers of the UI/Views framework:
1. ui/ozone:
- ui::PlatformSessionManager and ui::PlatformSessionWindowData: A new
ozone/public interface as well its accessor method in OzonePlatform,
with which client code (eg: chrome) can create and restore platform
sessions in a platform-neutral way.
2. ui/platform_window and ui/views:
- Add the widget and platform window init parameters/properties
required to plumb session info through from, e.g chrome, all the way
down to native widget => platform window implementation (ie:
ozone/wayland).
Further design notes available at
https://notes.nickdiego.dev/chromium/wayland-session-management
The upcoming CLs will add the remaining bits, including:
- Ozone/Wayland implementation based on xdg-toplevel-drag-v1 protocol.
- Chrome required plumbing and required changes.
R=fangzhoug
Bug: 352081012
Change-Id: Ie4dbcc559303c77d72b030b04c95ec933887855a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6329156
Reviewed-by: Avi Drissman <avi@chromium.org>
Auto-Submit: Nick Yamane <nickdiego@igalia.com>
Reviewed-by: Kramer Ge <fangzhoug@chromium.org>
Reviewed-by: Tom Lukaszewicz <tluk@chromium.org>
Commit-Queue: Nick Yamane <nickdiego@igalia.com>
Cr-Commit-Position: refs/heads/main@{#1438502}
ChromiumChromium 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.