Make autoclick app work in mash |
|||||
Issue descriptionNow that the window service is rolling out Ben suggested that we investigate making some of our smaller mojo apps work under mus, rather than waiting for mash. This would help other teams launch small features as mojo apps without having to wait for the full mash conversion. I'm going to investigate autoclick. Things to do: 1. Make it actually generate clicks. erg@ had to introduce a trusted event-generation interface to make remoting work (RemoteEventDispatcher), so I'll try using that. 2. Figure out what to do to get it to open a widget, paint, etc. 3. Change the launching code to look for feature Mus in addition to Mash.
,
Mar 14 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ef8990ce90516cfafd75f241d270e5489c0fc6e7 commit ef8990ce90516cfafd75f241d270e5489c0fc6e7 Author: James Cook <jamescook@chromium.org> Date: Wed Mar 14 21:06:36 2018 cros: Make autoclick work under mash Generate synthetic clicks and dispatch them via the window service. Add the remote event dispatcher interface to a new "accessibility" capability, available only to trusted apps. Bug: 821471, 628665 Test: Use autoclick on multiple displays with different scale factors Change-Id: I61352a0849a96a2bc0ae14d0b8afcca051ba67e2 Reviewed-on: https://chromium-review.googlesource.com/961668 Reviewed-by: Scott Violet <sky@chromium.org> Reviewed-by: Tom Sepez <tsepez@chromium.org> Commit-Queue: James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#543190} [modify] https://crrev.com/ef8990ce90516cfafd75f241d270e5489c0fc6e7/ash/autoclick/common/autoclick_controller_common_delegate.h [modify] https://crrev.com/ef8990ce90516cfafd75f241d270e5489c0fc6e7/ash/components/autoclick/DEPS [modify] https://crrev.com/ef8990ce90516cfafd75f241d270e5489c0fc6e7/ash/components/autoclick/autoclick_application.cc [modify] https://crrev.com/ef8990ce90516cfafd75f241d270e5489c0fc6e7/ash/components/autoclick/autoclick_application.h [modify] https://crrev.com/ef8990ce90516cfafd75f241d270e5489c0fc6e7/ash/components/autoclick/manifest.json [modify] https://crrev.com/ef8990ce90516cfafd75f241d270e5489c0fc6e7/services/ui/manifest.json
,
Mar 15 2018
I think touch HUD is a better first choice than autoclick for a mus mojo app. Putting this one on hold, pending discussion of how to do mus mojo apps in the first place.
,
Apr 19 2018
,
Aug 6
We went with touch hud and shortcut viewer. Autoclick is lower priority.
,
Aug 15
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by bugdroid1@chromium.org
, Mar 14 2018