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

Issue 897007 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Oct 26
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Cannot open on-screen keyboard after opening it from external screen

Project Member Reported by yamaguchi@chromium.org, Oct 19

Issue description

Chrome Version: 72.0.3585.0
Chrome OS Version: 11075.0.0
Chrome OS Platform: (caroline)

Steps To Reproduce:
(1) Set device in the laptop mode. Connect an external monitor.
(2) Enable "On-screen keyboard" in the Accessibility setting. See the keyboard icon appears in the shelf.
(3) Click the keyboard button on the external monitor.

Expected Result:
On-screen keyboard appears somewhere.

Actual Result:
On-screen keyboard does not appear, but the button stays activated.
After step 3, on-screen keyboard cannot be opened on the internal monitor using the keyboard button there. It continues until signing out.

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Always

What is the impact to the user, and is there a workaround? If so, what is
it?
The keyboard can be opened again after signing out and signing in again.

 
Also reproduced with 69.0.3497.120 / 10895.78.0 on Chromebook Pixel 2.
Owner: shend@chromium.org
Status: Assigned (was: Untriaged)
Labels: M-72
Project Member

Comment 4 by bugdroid1@chromium.org, Oct 24

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

commit fa88e291eb2a6ec6042bad34c7818ca040d1da28
Author: Darren Shen <shend@chromium.org>
Date: Wed Oct 24 22:38:22 2018

[VK] Fix full width virtual keyboard on multiple displays.

Full width virtual keyboard on multiple displays was broken because
we made an assumption that we only attach the virtual keyboard to
a root window at initialization. Actually, it can be called whenever
the keyboard changes displays. So we should actually be maintaining
the same bounds whenever we attach to a new root window.

Unfortunately, floating keyboard on multiple displays looks utterly
broken...but that's a separate issue.

Bug:  897007 
Change-Id: I6392a790cd172cd3899c2c0b3cfd41f31a096fbc
Reviewed-on: https://chromium-review.googlesource.com/c/1296948
Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602501}
[modify] https://crrev.com/fa88e291eb2a6ec6042bad34c7818ca040d1da28/ash/keyboard/virtual_keyboard_controller_unittest.cc
[modify] https://crrev.com/fa88e291eb2a6ec6042bad34c7818ca040d1da28/testing/buildbot/filters/chromeos.single_process_mash.ash_unittests.filter
[modify] https://crrev.com/fa88e291eb2a6ec6042bad34c7818ca040d1da28/ui/keyboard/keyboard_layout_manager.cc

Status: Fixed (was: Assigned)
Should be fixed now

Sign in to add a comment