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

@othermaciej Re: Geometry of the VK - This is mainly for devices with dual screen where the VisualViewport change only gives the rectangle that is occluded by the VK, but really the content that is occluded by the VK only covers one screen and not the other. [This explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/VirtualKeyboardAPI/explainer.md) has screenshots describing the dual screen in greater detail.
Also just to make sure that I understand it correctly, do we agree that iOS would benefit from the VK proposal? Do you have any immediate concerns that are specific to iOS that would affect the experience of the user because of authors manually controlling the VK?

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

Received on Wednesday, 8 April 2020 16:06:10 UTC