- From: Matt Reynolds <notifications@github.com>
- Date: Wed, 29 Oct 2025 17:58:38 -0700
- To: w3c/gamepad <gamepad@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/gamepad/issues/226/3465729775@github.com>
nondebug left a comment (w3c/gamepad#226) i. **Progress** – What has your spec achieved in the last 12 months? * Added the [GamepadTouch](https://w3c.github.io/gamepad/#gamepadtouch-interface) interface to support gamepads with one or more touch surfaces. * Added a [Model](https://w3c.github.io/gamepad/#model) section to define key gamepad concepts. * https://github.com/w3c/gamepad/issues/219 * Reviewed the current status of existing cross-browser and browser-specific Gamepad API web tests: [Evaluation of the existing gamepad testing frameworks across user agents](https://docs.google.com/presentation/d/1gK-W5mirGWdERgcpX8KAcwYJphRubz4eoQ-wdilyJZk/edit?usp=sharing) * Created a [manual interop test suite](https://github.com/web-platform-tests/interop-gamepad/blob/main/manual-tests.html) * Collaboratively executed the manual test suite to exercise real-world usage scenarios and identify key gaps and inconsistencies in browser behavior ([notes](https://docs.google.com/document/d/1oBV4K6rCZOn0p9XlMXBkLZBB-wcEPTUDtiCOwf_FusA/edit?tab=t.0#heading=h.xarlmp6z56ks)) * Defined interfaces for automation, laying the groundwork for future automated testing: https://github.com/w3c/gamepad/pull/224 ii. **Blockers** – Is anything preventing it from moving to CR or Rec? Poor test coverage. It not possible to write cross-browser automated web platform tests to exercise gamepad behaviors. iii. **Testing** – Is there a testing plan for this spec? Yes, we are developing an automation API to enable better test coverage. iv. **Next Steps** – How will you unblock it? Do you need help? For 2026, we plan to: * Implement the automation interfaces defined in 2025. * Develop initial automated tests for core Gamepad API functionality. * Validate test behavior across major browsers. * Identify and document remaining spec ambiguities or implementation inconsistencies. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/gamepad/issues/226#issuecomment-3465729775 You are receiving this because you are subscribed to this thread. Message ID: <w3c/gamepad/issues/226/3465729775@github.com>
Received on Thursday, 30 October 2025 00:58:41 UTC