New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 796365 link

Starred by 2 users
Status: Assigned
Owner:
shuchen@chromium.org
Cc:
█ bshe@chromium.org
satorux@chromium.org
jamescook@chromium.org
shend@chromium.org
steve...@chromium.org
omrilio@chromium.org
mustash-bugs@google.com
█ blakeo@chromium.org
yhanada@chromium.org
pcovell@chromium.org
█ dvallet@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug


Participants' hotlists:
Fixing-touch


Sign in to add a comment

Support RootWindowController::ActivateKeyboard in Mash

Project Member Reported by steve...@chromium.org, Dec 19 2017 
Currently we call ash::Shell::GetPrimaryRootWindowController()->ActivateKeyboard(keyboard::KeyboardController::GetInstance()) from ChromeBrowserMainExtraPartsAsh::PostProfileInit() (soon to be in ChromeBrowserMainPartsChromeos).

We need to determine where and how this should be done for Mash and fix it.

Comment 1 by jamescook@chromium.org, Dec 19 2017

Cc: satorux@chromium.org
Components: UI>Input>VirtualKeyboard
+satorux for potential virtual keyboard work item

Comment 2 by blakeo@chromium.org, Dec 20 2017

Owner: blakeo@chromium.org

Comment 3 by blakeo@chromium.org, Mar 26 2018

Owner: shend@chromium.org

Comment 4 by jamescook@chromium.org, Apr 19 2018

Components: Internals>Services>Ash
Labels: -Proj-Mustash-Mash

Comment 5 by benhenry@chromium.org, Aug 1

Status: Assigned (was: Available)

Comment 6 by shend@chromium.org, Sep 12

Cc: shend@chromium.org
Owner: shuchen@chromium.org
Hi Shu, do you mind taking this over since it's part of making VK work in MASH?
►

Sign in to add a comment