No virtual keyboard if BT stack is broken |
||||
Issue descriptionChrome Version: 71.0.3578.49 beta OS: Chrome User report from kanliu@: https://listnr.corp.google.com/product/5015361/report/85785278442 What steps will reproduce the problem? From offline email: 1. I opened up my mewoth/brydge 2. noticed that brydge kb wasn't working, checked quick settings menu and noticed bluetooth was missing 3. tried to enter password but no virtual kb came up 4. used fp to sign in 5. clicked file feedback report using touch and menu 6. noticed i couldn't type and couldn't get any virtual kb to show up including the accessibility one which i explicitly enabled and tried to click on the icon in the shelf for 7. ended up just finding an email with the term "bluetooth" and using touch to copy and paste in the feedback report :) What is the expected result? The device should switch to tablet mode and virtual keyboard should be usable What happens instead? Virtual keyboard is unusable
,
Nov 16
This bug requires manual review: M71 has already been promoted to the beta branch, so this requires manual review Please contact the milestone owner if you have questions. Owners: benmason@(Android), kariahda@(iOS), kbleicher@(ChromeOS), govind@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 16
How did the testing go on ToT?
,
Nov 16
Not sure. It's a random issue and the CL is a speculative fix, so hard to tell...
,
Nov 19
Let's keep working against ToT/M72 until we have better confidence on this fix. We're late in the M71 release cycle. If you get more confidence on M72 we can merge back into M71.
,
Dec 3
rejecting the merge request since we're late into M71 and no updates in some time.
,
Dec 18
The fix has landed in #1. Close this issue. Feel free to reopen if you can still see the issue.
,
Dec 18
|
||||
►
Sign in to add a comment |
||||
Comment 1 by x...@chromium.org
, Nov 16