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

**Meeting minutes:** https://www.w3.org/2020/10/30-editing-minutes.html
**Summary of the discussion:**
We discussed about the `VirtualKeyboard `APIs and how it affects UX on both dual and single screen devices. The presentation was mainly focused on describing the problems faced by web authors while dealing with virtual keyboard(VK) on touch devices where the VK is the primary source of text input for users. We showed a demo of the VK APIs and how the authors could use it to provide a much better UX experience on their sites.
Demo page: https://bocupp-microsoft.github.io/VirtualKeyboard/geometrychange.html
Slides:  https://cuppfamily-my.sharepoint.com/:p:/g/personal/bo_seattlecupps_com/EVoI7Hp5An1HokezOTE3hK0BLMT2UsL1k7-ryO8-8efv6w?e=EplB9S

**Issue discussions:**

- Concerns about VK APIs being abused and sites behaving poorly because of that:
   We currently have sticky user activation and active document as a requirement to restrict showing the VK. VK APIs are also an opt-in mechanism where authors have to explicitly indicate that they would like to control the VK behavior. Currently the show/hide behavior can be abused by using `inputMode `property.
- Is `navigator` the right place? 
  We didn't get a chance to discuss this in detail, but I haven't seen any objections in [this ](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/387)issue after the latest response.
- Relationship with the `VisualViewport `API and concerns in general regarding creating a separate API to handle overlaying of content in response to VK `show/hide`:
  We had extensive discussions on this issue. We generally agree that having a separate event describing the overlay property and geometry of the VK helps the authors make better decision as to how to position specific parts of the webpage in response to VK occluding the content of the webpage.
- Have VK `show/hide` APIs return a promise
  We all agreed that returning a promise when authors call `show/hide` helps to test the APIs and also make decisions when the calls failed to show/hide the VK. This needs more discussion as we are not entirely sure that returning an error code helps the authors in a meaningful way.
- We are also looking for collaborators to write a spec for these APIs.
@BoCupp-Microsoft Please let me know if I missed anything.

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