Issue 657107 link

Starred by 2 users

Issue metadata

Status:	Archived
Owner:	kylec...@chromium.org
Closed:	Jan 2017
Cc:	mustash-bugs@google.com
EstimatedDays:	----
NextAction:	----
OS:	Chrome
Pri:	3
Type:	Bug
Proj-Mustash-Mus VerifyIn-59 VerifyIn-60 VerifyIn-61

Move display::mojom::TestDisplayController into its own capability class

Project Member Reported by sky@chromium.org, Oct 18 2016

Issue description

Currently display::mojom::TestDisplayController is grouped in the capability class ui:window_manager. As TestDisplayController is really only for testing we should move it into its own capability class, maybe ui:window_manager-test or something.

Project Member

Comment 1 by bugdroid1@chromium.org, Jan 24 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/09b64d2271dec56ef2c739809abc499263926b69

commit 09b64d2271dec56ef2c739809abc499263926b69
Author: kylechar <kylechar@chromium.org>
Date: Tue Jan 24 20:42:37 2017

Move TestDisplayController into own capability class.

TestDisplayController isn't directly related to the window_manager
class and shouldn't be part of it.

BUG= 657107 

Review-Url: https://codereview.chromium.org/2652973003
Cr-Commit-Position: refs/heads/master@{#445797}

[modify] https://crrev.com/09b64d2271dec56ef2c739809abc499263926b69/ash/mus/manifest.json
[modify] https://crrev.com/09b64d2271dec56ef2c739809abc499263926b69/services/ui/manifest.json