w3c/gamepad Issues

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

15 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
#6	Should specify how to present d-pads/triggers as buttons	❌	9.7 years	9.6 years
#42	[Extensions] When does `GamepadHapticActuator#pulse` resolve `false` or reject?	❌	8.2 years	8.2 years
#92	Move deprecated WebVR-specific extensions to WebVR	❌	5.7 years	5.7 years
#110	Define enumeration behavior when a gamepad is emulated with WebXR input devices.	❌	5.3 years	5.2 years
#128	Direction and thrust of the joystick	❌	4.7 years	4.7 years
#134	Rewrite gamepad spec using algorithms	❌	4.5 years	4.5 years
#139	Consider how to support devices like Apple Remote	❌	4.4 years	4.3 years
#175	Add a means to test the API	❌	2 years	2 years
#199	Vendor ID, product ID, name attributes	❌	8.4 months	8.1 months
#200	GamepadHapticActuator promises issues	❌	8.4 months	8.1 months
#206	Require focus for initial gamepad user gesture	❌	7.4 months	7.2 months
#212	[gamepad] Missing tasks in parallel steps in Gamepad	❌	3.4 months	3.2 months
#213	Units used in the GamepadPose Interface look weird	❌	3 months	2.8 months
#214	Suggest on the mechanism for the user authorization for gamepads	❌	2.8 months	2.6 months
#216	eventInitDict parameter in GamepadEvent constructor should be optional	❌	2.4 months	2.1 months