New issue
Advanced search Search tips

Issue 631817 link

Starred by 2 users
Status: WontFix
Owner:
riajiang@chromium.org
Closed: Mar 2017
Cc:
sadrul@chromium.org
mustash-bugs@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Mus needs test interface for generating events

Project Member Reported by sky@chromium.org, Jul 26 2016 
Without it we won't have a sane way to ensure events are correctly processed end-to-end. I suspect we'll also need to make sure ui_test_utils works correctly with it, but that can be done later.

Comment 1 by sky@chromium.org, Jul 26 2016

Blocking: 631819

Comment 2 by rjkroege@chromium.org, Aug 8 2016

Cc: sadrul@chromium.org
Owner: riajiang@chromium.org

Comment 3 by sadrul@chromium.org, Aug 8 2016

Status: Available (was: Untriaged)
We should be able to use the same interface for accessibility/autoclick ( issue 628665 )

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

Labels: Proj-Mustash

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

Components: Internals>MUS

Comment 6 by mfomitchev@chromium.org, Dec 9 2016

Labels: Proj-Mustash-Testing
Does WindowTreeClientPrivate::CallOnWindowInputEvent address the need, or do we need something more?

Comment 7 by sadrul@chromium.org, Dec 9 2016

Labels: Proj-Mustash-Mus-WS
That generates event from the client-side. It can't be used to, for example, generate an event from a client that is targeted to a different client.

Comment 8 by riajiang@chromium.org, Mar 22 2017

Status: WontFix (was: Available)
sadrul@ mentioned that this has already been fixed by erg@ in https://codereview.chromium.org/2759463002/

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

Components: -Internals>MUS Internals>Services>WindowService

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

Components: -MUS

Comment 11 by sky@chromium.org, Aug 13

Blocking: -631819
►

Sign in to add a comment