After switching to floating keyboard, in lock screen, users can't switch back to full keyboard |
|||||||||||
Issue descriptionChrome Version: (copy from chrome://version) OS: (e.g. Win10, MacOS 10.12, etc...) What steps will reproduce the problem? (1)After logging into Chrome OS, switch to floating virtual keyboard in tablet mode (2)Log out (3)Try to log in, virtual keyboard shows up as floating keyboard, but can't be switched back to full keyboard What is the expected result? Users should be able to switch back to full keyboard What happens instead? Users can't switch back to full keyboard Please use labels and text to provide additional information. If this is a regression (i.e., worked before), please consider using the bisect tool (https://www.chromium.org/developers/bisect-builds-py) to help us identify the root cause and more rapidly triage the issue. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Aug 14
Blocked on UX feedback.
,
Aug 15
Chatted offline with Omri and Jason, we agree that we should just show the full VK on lock screen for M70. Confirming with the Gboard team in the deck: https://docs.google.com/presentation/d/1pHF2dkf2dEz0TOAz839vQBm8SsRDz40gYHaoQ_5lJm0/edit#slide=id.g3d4df828d1_3_57
,
Aug 15
Hi Yingbing, do you know how to actually do this? I'm guessing it has to be done on the extension side. Does IME extension know when it's in the lock screen?
,
Aug 28
,
Sep 4
Should not allow to switch to floating keyboard in login/lock screen.
,
Sep 4
,
Sep 4
seems the commit hasn't show up yet: https://chrome-internal-review.googlesource.com/c/chromeos/overlays/chromeos-overlay/+/671691
,
Sep 4
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/overlays/chromeos-overlay/+/f01ab2c43a24421f085b52967965f20e86faa33e commit f01ab2c43a24421f085b52967965f20e86faa33e Author: Li Zhao <iloahz@google.com> Date: Tue Sep 04 14:29:47 2018
,
Sep 4
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/overlays/chromeos-overlay/+/f01ab2c43a24421f085b52967965f20e86faa33e commit f01ab2c43a24421f085b52967965f20e86faa33e Author: Li Zhao <iloahz@google.com> Date: Tue Sep 04 14:29:47 2018
,
Sep 4
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/overlays/chromeos-overlay/+/f01ab2c43a24421f085b52967965f20e86faa33e commit f01ab2c43a24421f085b52967965f20e86faa33e Author: Li Zhao <iloahz@google.com> Date: Tue Sep 04 14:29:47 2018
,
Sep 5
,
Sep 5
Your change meets the bar and is auto-approved for M70. Please go ahead and merge the CL to branch 3538 manually. Please contact milestone owner if you have questions. Owners: benmason@(Android), kariahda@(iOS), geohsu@(ChromeOS), abdulsyed@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 6
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/overlays/chromeos-overlay/+/bda981c91b7790f0d8352adf422074a82a5ee2cf commit bda981c91b7790f0d8352adf422074a82a5ee2cf Author: Li Zhao <iloahz@google.com> Date: Thu Sep 06 04:51:24 2018
,
Sep 10
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 11
|
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by kejiashao@chromium.org
, Aug 10