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

> This means that the content under the keyboard is effectively unreachable unless the keyboard is dismissed, right?

Yes, unless the author uses the proposed CSS `env(keyboard-inset-*)` variables or `geometrychange` JS event to update the layout of the page.

> VisualViewport was meant to address exactly this kind of scenario (along with position: device-fixed which IIRC Edge/IE implemented) but unfortunately didn't foresee the multi-screen use case.

I think there are more scenarios than just multi-screen that make `device-fixed` unsuitable.  How would you implement the [canvas spreadsheet scenario mentioned in the explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/VirtualKeyboardAPI/explainer.md#repositioning-content-using-javascript)?

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