Re: [w3c/gamepad] TPAC 2026 Status Report (Issue #232)

nondebug left a comment (w3c/gamepad#232)

* **What progress have you made on your spec in the last 12 months?**
  * The [gamepad user gesture](https://w3c.github.io/gamepad/#dfn-gamepad-user-gesture) now requires [system focus](https://html.spec.whatwg.org/multipage/interaction.html#system-focus) to avoid unintentional exposure of gamepad state in inactive tabs. #207
  * A pull request to add input change events is in review and an experimental implementation is in [origin trial in Chromium](https://chromestatus.com/feature/5989275208253440). #234
  * The GamepadButton.type attribute is added to enable cross-implementation identification of buttons that do not have a standardized index. There is an [experimental implementation Chromium](https://chromestatus.com/feature/5075054393163776). #191
  * Merged #217 to resolve #216 eventInitDict parameter in GamepadEvent constructor should be optional.
  * Reviewed a proposal for [PCM-based haptics](https://cabanier.github.io/gamepad-haptics/).
  * Reviewed the [Web Haptics API explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Haptics/explainer.md) and discussed applicability to Gamepad API.
* **What blockers, if any, are preventing you from progressing your spec to CR or Req?**
  * Poor test coverage. It's not possible to write cross-browser automated web platform tests to exercise gamepad behaviors.
  * The current test automation proposal (#224) requires WebDriver BiDi, which is not fully implemented across all browsers.
* **Is there a testing plan for your spec?**
  * Automated test coverage is currently not sufficient. For Interop 2027 we [propose](https://github.com/web-platform-tests/interop/issues/1454) to continue our [Interop 2025 investigation effort](https://github.com/web-platform-tests/interop-gamepad) started in 2025 to provide an automation API for simulating gamepad inputs.
* **What are the next steps for your spec and do you need any help?**
  * Implement the automation interfaces defined in #224.
  * Develop initial automated tests for core Gamepad API functionality.
  * Validate test behavior across major browsers.
  * Identify and document implementation inconsistencies.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/issues/232#issuecomment-6067884898
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/gamepad/issues/232/6067884898@github.com>