-
Notifications
You must be signed in to change notification settings - Fork 3
Issues: w3c/virtual-keyboard
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[Virtual Keyboard API] Return promise for Show/Hide calls?
#2
opened Aug 6, 2021 by
travisleithead
updated Aug 23, 2021
Confusion about "viewport" terminology in the illustrations
#9
opened Aug 26, 2021 by
bramus
updated Aug 26, 2021
Privacy section doesn't explain measures enough
#12
opened Sep 2, 2021 by
jonathanKingston
updated Sep 24, 2021
[Virtual Keyboard API] A declarative mechanism to enable overlaycontent?
#3
opened Aug 6, 2021 by
travisleithead
updated Aug 11, 2022
We should be precise about how show/hide relies on user activation
#6
opened Aug 6, 2021 by
travisleithead
updated Sep 16, 2022
Add a javascript property/API to query the support of the Virtual Keyboard
#19
opened Nov 10, 2022 by
dpierangeli
updated Nov 10, 2022
Where is the dispatch of geometrychange events defined?
#21
opened Jul 31, 2023 by
birtles
updated Jul 31, 2023
overlayContent=false is misleading in fullscreen mode -- potential solution: boundingRect should be available regardless of overlayContent value?
#22
opened Dec 28, 2023 by
josephrocca
updated Dec 28, 2023
hide() method not working in manual mode on Android (Chrome)
#23
opened Jan 4, 2024 by
bschraml
updated Jan 4, 2024
Get VK’s
boundingRect before it is shown (beforegeometrychange event)
#24
opened Mar 14, 2024 by
bramus
updated Oct 23, 2024
Missing tasks in parallel steps in VirtualKeyboard API
#25
opened Jan 30, 2025 by
dontcallmedom-bot
updated Jan 30, 2025
2 tasks
ProTip!
Find all open issues with in progress development work with linked:pr.