Issue metadata
Sign in to add a comment
|
Regression: Windows 10 (Tablet Mode) Onscreen Keyboard Doesn't Open For Text Input
Reported by
dsander...@ucsbalum.com,
Aug 16
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 Steps to reproduce the problem: 1. Use Windows 10 in Tablet Mode (Specifically I tested with Surface Pro 4) 2. Go to http://jsfiddle.net/wqhjp9e5/ 2. Click in text box with placeholder "Broken" What is the expected behavior? Onscreen keyboard should open What went wrong? No onscreen keyboard opens Did this work before? Yes 68.0.3440.84 Chrome version: 68.0.3440.106 Channel: stable OS Version: 10 Flash Version: Works in 68.0.3440.84 and Canary. The regression occurred somewhere between 68.0.3440.84 and 68.0.3440.106.
,
Aug 16
Unable to reproduce the issue on Win-10(surface pro) using chrome reported version #68.0.3440.106. Attached a screen cast for reference. Following are the steps followed to reproduce the issue. ------------ 1. Used Windows 10 in Tablet Mode. 2. Navigated to http://jsfiddle.net/wqhjp9e5/ 3. Clicked in text box with placeholder "Broken" 4. Observed that Onscreen keyboard opened without any issues. reporter@ - Could you please check the issue by creating a new profile without any apps and extensions and please let us know if the issue still persist or not. Also please check the attached screen cast and please let us know if anything missed from our end. Thanks...!!
,
Aug 16
#2, thanks for the quick response. The screen cast does look like correct reproduction, no idea why it works on that one but not mine. Only difference I see from chrome://version is the screen cast is 32-bit, mine is 64-bit. I've tested with a new profile, and there are no extensions installed (besides the default Google ones). I also tried uninstalling Chrome and installing it again (although it kept the browsing history and bookmarks) and the issue still reproduces.
,
Aug 16
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 17
The issue looks similar to issue id: 491516. Hence, merging into the issue id: 491516. Please feel free to undupe the same if not the case. Thanks...!! |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by phanindra.mandapaka@chromium.org
, Aug 16