TPAC 2025 status report

[siusin]

TPAC 2025 will be hybrid.

The WebApps Working Group will meet in Kobe, Japan (and online) on:

• Monday 10 Nov
• Tuesday 11 Nov
• Thursday 13 Nov

If you plan to attend, either in person or remotely, please register here.

---

Editors, we need you to do two things before 30 October 2025:

• If you’d like to discuss your spec(s), add the label TPAC2025 to the relevant GitHub issues.
• Complete a status report for your spec(s)

Status report

• Please post your status report as a comment on this issue.

• Your report should answer:

  1. Progress – What has your spec achieved in the last 12 months?
  2. Blockers – Is anything preventing it from moving to CR or Rec?
  3. Testing – Is there a testing plan for this spec?
  4. Next Steps – How will you unblock it? Do you need help?

Note: Submit a status report even if you will not attend TPAC.

[marcoscaceres]

@nondebug, ping 🙏

[diekus]

@nondebug, ping² 🙂

[nondebug]

i. Progress – What has your spec achieved in the last 12 months?

• Added the GamepadTouch interface to support gamepads with one or more touch surfaces.
• Added a Model section to define key gamepad concepts.
• Interop 2025 investigation effort - Gamepad API testing #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
  • Refined the manual test API to better reflect real-world usage scenarios and identify key gaps and inconsistencies in browser behavior (notes)
  • Defined interfaces for automation, laying the groundwork for future automated testing: Integrate with WebDriver and WebDriver BiDi for automation #224
  • Created a manual interop test suite and collaboratively executed it to identify inconsistent behavior between browser engines. (notes)

ii. Blockers – Is anything preventing it from moving to CR or Rec?

Poor test coverage. It's 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.

[SteveBeckerMSFT]

For 2026, Microsoft is also interested in working on the following issues:

• Gamepad Input Events
  • Started prototyping in Chromium
• Web worker support

[marcoscaceres]

Great! Thanks for adding the labels @SteveBeckerMSFT! Looking forward to discussing those at TPAC.