merge window mappings in WindowServer |
||||
Issue descriptionCurrently we have three mappings in WindowServer for each client: 1. WindowId -> ClientWindowId (https://cs.chromium.org/chromium/src/services/ui/ws/window_tree.h?type=cs&pv=1&l=664) 2. ClientWindowId -> WindowId (https://cs.chromium.org/chromium/src/services/ui/ws/window_tree.h?type=cs&pv=1&l=662) 3. WindowId -> ServerWindow (https://cs.chromium.org/chromium/src/services/ui/ws/window_tree.h?type=cs&pv=1&l=656) ServerWindow has an id_ field for WindowId and a frame_sink_id_. Now that frame_sink_id_ is the ClientWindowId, we can have two mappings instead: 1. WindowId -> ServerWindow 2. ClientWindowId -> ServerWindow which should cover all use cases that we have in WindowServer.
,
Apr 24 2018
Deprecating label Proj-Mustash-Mus-WS in favor of Components.
,
Apr 24 2018
Migrating Proj-Mustash-Mus to components Internals>Services>WindowService and Internals>Services>Ash
,
Aug 15
We are down to two now: aura::Window->ClientWindowId ClientWindowId->aura::Window* |
||||
►
Sign in to add a comment |
||||
Comment 1 by lafo...@chromium.org
, Feb 26 2018