Re: [w3ctag/design-reviews] VirtualKeyboard API - show/hide policy (#498)

Thank you everyone for all the feedback!
@cynthia @annevk [This ](https://github.com/whatwg/html/issues/4876)issue specifically talks about inputMode attribute and [this ](https://github.com/whatwg/html/issues/4876#issuecomment-585485280)comment was about deprecating inputMode="none"'s special behavior of hiding the VK which we believe is conflating two different states and doesn't cover some of the scenarios mentioned in the [explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/VirtualKeyboardPolicy/explainer.md). This feature gives explicit control of the VK to the web authors. It also defines an attribute that differentiates between the custom (virtualKeyboardPolicy="manual") and default(virtualKeyboardPolicy="auto")  VK behavior. When virtualKeyboardPolicy is "manual", inputMode ="none" 's hiding of the keyboard state is ignored, but the default VK layout is kept intact. Basically, with virtualKeyboardPolicy attribute, the web authors could control the VK behavior without affecting the layout of the VK which would be controlled by the inputMode attribute. These two states (visibility and layout of the VK) are kept separate in this proposal so web authors can use it to facilitate more complicated scenarios on their sites.
The new API can be feature-detected by checking for the existence of the virtualKeyboard property on the navigator object.

@kenchris [This ](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/VirtualKeyboardPolicy/explainer.md#background-and-motivating-scenarios)section talks about the range-peeking scenario in Excel that sort of merges the two use cases that were mentioned in [this ](https://github.com/whatwg/html/issues/4876#issuecomment-541232517)comment, but I agree that we should explicitly mention that in the explainer. I'll create an issue in our repo and address that in the explainer.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/498#issuecomment-617309931