The two explainers above were developed in parallel and describe two aspects of the same interface:VirtualKeyboard, which we intend to prototype.
The new VirtualKeyboard interface enables authors to:
See the explainers for motivating scenarios.
Interoperability and Compatibility
This API allows sites that want fine-grained control over their editing and input experience to progressively enhance how users interact with their site on touch-first
devices using the VK.
The new API can be feature-detected by checking for the existence of the virtualKeyboard property on the navigator object.
Edge: Public support
Chrome: Public support
Firefox: No signals
Safari: No signals
Github issues: https://github.com/whatwg/html/issues/4896
Are there any other platform APIs this feature will frequently be used in tandem with?
Could the default usage of this API make it hard for Chrome to maintain good performance (i.e. synchronous return, must run on a certain thread, guaranteed return timing)?
Will it be challenging for developers to take advantage of this feature immediately, as-is?
Would this feature benefit from having polyfills, significant documentation and outreach, and/or libraries built on top of it to make it easier to use?
No, as the web APIs need to interact with system VK APIs which is currently not possible through JS.
These APIs are just a trigger for the system VK APIs so currently there is no support for web developers to debug system VK APIs through dev-tools. No specialized debugging experience is currently envisioned.
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
No. This API is appropriate for touch-first devices such as phones and tablets where the on-screen keyboard is the primary input method. Windows, Android and Chrome OS are candidates.
We are seeking collaborators with platform expertise to help with non-Windows implementations.
Link to entry on the feature dashboard
Requesting approval to ship?
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/SN2PR00MB00934435C1DE1ABA33572F78CFD20%40SN2PR00MB0093.namprd00.prod.outlook.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAABs73hcVxXOB15nBFps2WkPo1GjsGNk2MSOx%3DB02LMz%2BZUmsw%40mail.gmail.com.
autocauses the corresponding editable element to automatically show the VK when it is focused or tapped (current behavior);
manualdecouples focus and taps on the editable element from changes in the VK’s current state - the VK remains as it was."
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2Bm%3DdJqZ6h6xAzyNaA3QRUmDueDNg1Kw7Ona_uaH-wU04aq72g%40mail.gmail.com.