w3c/virtual-keyboard Issues

Last updated May 17, 2024, 5:57:32 AM UTC.

This repository doesn't have the Priority: Eventually label that's used to mark an issue as triaged without giving it an SLO. Until that's added, this summary uses heuristics to guess if each issue has been triaged.

9 out-of-SLO untriaged issues

Untriaged

Try to triage issues within 7 days. [ More Info ]

Issue	Title	Within SLO	On maintainers' plates for	Time past SLO
#2	[Virtual Keyboard API] Return promise for Show/Hide calls?	❌	2.8 years	2.8 years
#5	Relationship with `VisualViewport`	❌	2.8 years	2.8 years
#9	Confusion about "viewport" terminology in the illustrations	❌	2.7 years	2.7 years
#18	New features	❌	1.8 years	1.8 years
#19	Add a javascript property/API to query the support of the Virtual Keyboard	❌	1.5 years	1.5 years
#21	Where is the dispatch of geometrychange events defined?	❌	9.6 months	9.3 months
#22	`overlayContent=false` is misleading in fullscreen mode -- potential solution: `boundingRect` should be available regardless of `overlayContent` value?	❌	4.6 months	4.4 months
#23	hide() method not working in manual mode on Android (Chrome)	❌	4.4 months	4.2 months
#24	Get VK’s `boundingRect` before it is shown (`beforegeometrychange` event)	❌	2.1 months	1.9 months