Re: [w3c/editing] inputPanelPolicy as a way to control software keyboard (#225)

@othermaciej as I understand it the Visual Viewport API describes the viewport, not the on screen keyboard.  Certainly the keyboard can influence the size of the viewport - so can resizing the browser - but in my mind that doesn't make a viewport API an ideal API surface for controlling or describing the the on screen keyboard.

In these two explainers: [Virtual Keyboard API](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/VirtualKeyboardAPI/explainer.md), [Virtual Keyboard Policy](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/VirtualKeyboardPolicy/explainer.md) we describe the capabilities of the virtual keyboard API:
* requesting that the keyboard be shown
* requesting the the keyboard be hidden
* providing events for when the keyboard is shown or hidden
* providing the size of the keyboard (which will not be the full width of the viewport on some devices)
* instructing the keyboard to not automatically resize the viewport

As an author I would be surprised to find all these keyboard related capabilities on a viewport API.  The only connection to the viewport is the ability to request that the keyboard not resize the viewport when shown.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/225#issuecomment-614902156