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

Issue 838803 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Floating Keyboard disappears once switch to A11y

Project Member Reported by xiulingw@chromium.org, May 2 2018

Issue description

Version 68.0.3416.0(Official build) canary (64 bit)
Platform 10635.0.0(official build) canary-channel link 
Firmware Google_Link.2695.1.169


REPRO STEPS:
1.Switch to any Floating keyboard
2.Switch to A11y
3.Click on the input-box

Actual result:
Keyboard does not pop up. 

Note:
Keyboard still not pop up, even after i switch another language or click Emoji/HW/Voice icon from the opt-menu, or switch back to Input view layout.

This issue does not repro for Dock mode.


 
May 2 2018 3_46 PM.webm
4.3 MB View Download
Owner: iloahz@chromium.org
Cc: yhanada@chromium.org
Hi Hanada, can you help take a look at this issue?

Some findings:
1. When virtual keyboard doesn't show up, looks like the tab for IME's UI(title: Chrome OS Virtual Keyboard) is totally hidden.
2. Chrome 67.0.3396.26 with latest IME code doesn't have this issue.

I thought it could be related to recent chrome changes, can you help take a look?
Cc: jzfeng@chromium.org
I will take a look tomorrow.
Cc: shend@chromium.org
Checked that this bug is introduced by https://chromium-review.googlesource.com/c/chromium/src/+/1025532.

Darren, could you help to take a look?

Thanks!

Comment 6 by shend@chromium.org, May 3 2018

Hmm probably something to do with KeyboardController's destructor...since we're not calling it anymore. I'll take a look. If I can't figure it out, I've got a revert here: https://chromium-review.googlesource.com/c/chromium/src/+/1041445

Comment 7 by shend@chromium.org, May 3 2018

Cc: -shend@chromium.org iloahz@chromium.org
Owner: shend@chromium.org

Comment 8 by shend@chromium.org, May 3 2018

It seems like it's stuck in LOADING_EXTENSION state, but not sure why. Resetting the container behaviour when we reset the UI seems to fix it, but I have no idea why.

Comment 9 by shend@chromium.org, May 4 2018

Status: Fixed (was: Assigned)
Reverted the patch, seems to have fixed it. I'll need to rethink how to do that patch.
Status: Verified (was: Fixed)
Verified fixed on the latest veraion: 69.0.3480.0,10848.0.0 kevin.

Sign in to add a comment