mozilla / standards-positions

https://mozilla.github.io/standards-positions/
Mozilla Public License 2.0
615 stars 69 forks source link

Virtual Keyboard Control #531

Open snianu opened 3 years ago

snianu commented 3 years ago

Request for Mozilla Position on an Emerging Web Specification

Other information

TAG review threads: https://github.com/w3ctag/design-reviews/issues/507 https://github.com/w3ctag/design-reviews/issues/498

TPAC discussions where we discussed about the VK API shape and events: https://www.w3.org/2020/10/TPAC/breakout-schedule.html#virtual-keyboard https://www.w3.org/2020/10/30-editing-minutes.html 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

Thanks!

snianu commented 3 years ago

Gentle ping.. Tagging few people for feedback @annevk @smaug----

mseddon commented 2 years ago

This is actually a big deal, the kludges required to work around virtual keyboard issues on mobile browsers are horrible.

chrishtr commented 2 years ago

Hi, I'm wondering if Mozilla has a position on this API. Virtual keyboards do seem to be a large complaint from developers.

This API could also have a significant impact on the Viewport Interop 2022 investigation area (example; see discussion of overlaysContent).

woody-li commented 1 year ago

Is it possible to implement virtualKeyboard.boundingRect and geometrychange event firstly. Most needs in mobile device are related to get keyboard size and attach its toggle event.