WICG/input-device-capabilities Issues

Last updated Dec 22, 2024, 5:46:10 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.

13 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
#4	Add tests for non-input events?	❌	9.5 years	9.5 years
#9	Need more precise W3C language / formatting	❌	9.5 years	9.5 years
#12	Should init*Event methods clear the sourceDevice?	❌	9.5 years	9.4 years
#13	Touch not detected properly on Windows Phone	❌	9.5 years	9.4 years
#25	Add a supportsPointerPressure property?	❌	8.2 years	8.2 years
#26	API to indicate a device relies on focus afforadances	❌	8.2 years	8.2 years
#27	Improve reliability of mouse event from touch interaction in polyfill	❌	8.1 years	8.1 years
#30	Upstream tests to web-platform-tests	❌	7.2 years	7.2 years
#31	Enumerate devices	❌	6.7 years	6.6 years
#39	Suggest adding a `firesHoverEvents` property or some way to detect that in active input device supports hover?	❌	2.7 years	2.6 years
#40	Suggest adding a `isCoarse` property?	❌	2.7 years	2.6 years
#41	Suggest adding an event for `PointerInputDeviceChanges`	❌	2.7 years	2.6 years
#42	Focus events and keyboard navigation	❌	2.2 years	2.2 years