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

@smaug---- @othermaciej We didn't want to describe the Visual Viewport with a path instead of a rectangle, i.e. let's not create L-shaped viewports.

The [Virtual Keyboard API](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/VirtualKeyboardAPI/explainer.md) includes a property "overlaysContent" which tells the browser not to resize the Visual Viewport in response to the appearance of a docked VK.  Setting this property true opts in to separate keyboard geometry events and stops reducing the size of the Visual Viewport so as not to waste space in dual screen scenarios.

It is specifically because we're not changing the size of the Visual Viewport that we didn't extend the existing API.

-- 
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-613035634