New issue
Advanced search Search tips

Issue 679782 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Team-Accessibility

Blocked on:
issue 888145
issue 648733



Sign in to add a comment

Make TouchExplorationManager and TouchExplorationControllerDelegate work with ash-mus

Project Member Reported by sky@chromium.org, Jan 10 2017

Issue description

These classes likely need changes to mus to work, but I could be wrong.
 
Components: Internals>Services>Ash
Labels: -Proj-Mustash-Mash
Labels: -Proj-Mustash-Mus-WS
Deprecating Proj-Mustash-Mus-WS label in favor of Components.
Cc: msw@chromium.org steve...@chromium.org
Components: UI>Accessibility
Labels: Proj-Mash-SingleProcess
Status: Available (was: Untriaged)
My guess is this will work for SingleProcessMash if we fix the virtual keyboard (these classes depend on virtual keyboard).

Blockedon: 648733
Summary: Make TouchExplorationManager and TouchExplorationControllerDelegate work with ash-mus (was: Make AshTouchExplorationManager and TouchExplorationControllerDelegate work with ash-mus)
Cc: dmazzoni@google.com
Components: Internals>Input>Touch>Screen
I'm not sure if this is blocked on the virtual keyboard at all, it seems to work in SingleProcessMash for the status tray, etc. but not for Chrome's windows. I think SingleProcessMash support is actually just blocked on Issue 888145.
Blockedon: 888145
Labels: -Proj-Mash-SingleProcess Proj-Mash-MultiProcess
Moving to multi-process label, since the touch exploration code itself seems to be hooked up correctly for single-process mash.

Sign in to add a comment