The same On-screen Keyboard pops up on Windows 10 tablet mode regardless of the input type
Reported by
diego.me...@lushbrazil.com,
Feb 21 2018
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Steps to reproduce the problem: 1. Create a page with a <form> and inside it, an <input type="number">, an <input type="text"> and <input type="email"> 2. On Windows 10 2 in 1 computer, run Chrome on Tablet mode What is the expected behavior? The On-screen Keyboard should be different for each input type. For type "email", for example, it should show the special characters like "@", ".com", etc. For the type "number", it should only show numbers. What went wrong? the Keyboard that pops up is always the Text kind. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 64.0.3282.140 Channel: stable OS Version: 10 Flash Version: *Microsoft Edge works fine and shows the correct keyboard all the time
,
Feb 22 2018
,
Feb 23 2018
@Reporter: Please provide sample URL/test file to check this issue from TE end. This would help in further triaging of the issue. Thanks!
,
Mar 2 2018
The website http://www.456bereastreet.com/lab/html5-input-types/ can reproduce the problem.
,
Mar 2 2018
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
,
Mar 26 2018
,
Mar 26 2018
Hi Dave, it looks like the Windows OSK code doesn't trigger different keyboards based on input type [1]. Is this something you would like to take on? It seems like you can customize the keyboard layout with TabTip [2], but it might have the full set of layouts. [1] https://cs.chromium.org/chromium/src/ui/base/win/on_screen_keyboard_display_manager_tab_tip.cc?q=OnScreenKeyboardDisplayManagerTabTip&sq=package:chromium&l=298 [2] https://stackoverflow.com/questions/15646684/windows-8-desktop-app-open-tabtip-exe-to-secondary-keyboard-for-numeric-textbo
,
Mar 26 2018
You can send this to me if you like. I'm working on replacing TabTip with InputPane.. but I do believe we are populating the InputScope but I'll need to debug it.
,
Mar 26 2018
Thanks!
,
Jun 22 2018
Issue 855357 has been merged into this issue.
,
Jun 22 2018
> it looks like the Windows OSK code doesn't trigger different keyboards based on input type It does (see my issue 855357 ) but after reactivating the window. Workarounds from [2] do not work in Win 10 anymore :(
,
Jul 25
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by sindhu.chelamcherla@chromium.org
, Feb 21 2018