This issue has been automatically relabelled type=task because type=launch-owp issues are now officially deprecated. The deprecation is because they were creating confusion about how to get launch approvals, which should be instead done via type=launch issues.
We recommend this issue be used for implementation tracking (for public visibility), but if you already have an issue for that, you may mark this as duplicate.
For more details see here: https://docs.google.com/document/d/1JA6RohjtZQc26bTrGoIE_bSXGXUDQz8vc6G0n_sZJ2o/edit
For any questions, please contact owencm, sshruthi, larforge
Something to note about https://chromium-review.googlesource.com/c/chromium/src/+/850945
It might be worth noting that, on Android, inputmode="none" does not guarantee that keyboard remains hidden because of the peculiarities of how Android handles a physical keyboard.
Here are some observations from my testing:
1) Physical keyboard works without calling ‘showSoftInput’, although most IMEs don’t show UIs until you type the first key.
2) When you have turned on ‘Show virtual keyboard’, typing a physical key shows virtual keyboard even when you never call ‘showSoftInput’.
3) When you haven't turned on 'Show virtual keyboard', then 'showSoftInput' does not show virtual keyboard.
Because of 2) and 3), there is no way to ensure the keyboard to be hidden, and I think it makes sense to reuse the existing logic as much as possible.
This is something that wasn't clear to me, so some of my initial review comments might have been misleading. Assuming that we have no easy workaround for this limitation on Android anyways, I think we can go ahead with the current approach. Let me resume the code review.
Comment 1 by dtapu...@chromium.org
, Sep 27 2016