Chromium Code Reviews
Help | Chromium Project | Gerrit Changes | Sign in
(2)

Issue 2684623002: [WIP] Move ownership of PlatformDisplay from ws::Display to ws::WindowServer (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
4 months, 2 weeks ago by fwang
Modified:
4 months, 1 week ago
Reviewers:
kylechar, tonikitoo
CC:
chromium-reviews, rjkroege, Fady Samuel, sky
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

Move ownership of PlatformDisplay from ws::Display to ws::WindowServer In mash mode, an instance of ws::PlatformDisplay used for a drawable root window is currently owned by ws::Display which means we have to create a new display for each platform window. This works well for the "internal window mode" used by Chrome OS (a single drawable surface for the whole display). However, for "external window mode" (any number of plaform windows, each with their own drawable surface) the top level Chrome ServerWindows need to own ws::PlatformDisplay. This CL thus moves ownership of PlatformDisplay from ws::Display to ws::WindowServer. BUG=666958

Patch Set 1 #

Messages

Total messages: 10 (6 generated)
fwang
I'm not sure we have an agreement on how to implement external window mode precisely. ...
4 months, 2 weeks ago (2017-02-07 16:27:27 UTC) #2
kylechar
On 2017/02/07 16:27:27, fwang wrote: > I'm not sure we have an agreement on how ...
4 months, 2 weeks ago (2017-02-08 14:28:17 UTC) #8
kylechar
On 2017/02/08 14:28:17, kylechar wrote: > On 2017/02/07 16:27:27, fwang wrote: > > I'm not ...
4 months, 2 weeks ago (2017-02-09 18:03:05 UTC) #9
fwang
4 months, 1 week ago (2017-02-16 08:42:00 UTC) #10
Yes, I believe we can just continue to create an ws::Display (maybe renaming it)
for each external window. Closing this.
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld cb946e318