New issue
Advanced search Search tips

Issue 611977 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Aug 13
Cc:
sadrul@chromium.org
sky@chromium.org
mustash-bugs@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

TestScreen should not create native WindowTreeHost when in mus

Project Member Reported by sadrul@chromium.org, May 14 2016 
TestScreen::CreateHostForPrimaryDisplay() creates the 'default' WindowTreeHost instance on the client-side. This means, when building on X11, it creates a WindowTreeHostX11 instance, on the mus-client side. But mus-clients should not talk directly to the native platform (i.e. X11). This should be fixed.

One option is to create a platform-independent WindowTreeHost instance. (e.g. a WindowTreeHostPlatform with a ui::StubWindow)

Comment 1 by rjkroege@chromium.org, Oct 4 2016

Components: Internals>MUS
Labels: Proj-Mustash
Project Member

Comment 2 by sheriffbot@chromium.org, Oct 5 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 3 by lafo...@chromium.org, Feb 26 2018

Components: -Internals>MUS Internals>Services>WindowService

Comment 4 by lafo...@chromium.org, Feb 26 2018

Components: -MUS

Comment 5 by sky@chromium.org, Aug 13

Status: WontFix (was: Untriaged)
Too much code assumes otherwise, so TestScreen does create a WindowTreeHost when run with mus. One key difference is that when run in mus TestScreen creates a WindowTreeHostMus.
►

Sign in to add a comment