TPAC 2025 status report

[siusin]

TPAC 2025 will be hybrid.

There will be a Devices and Sensors Working Group and WebApps Working Group Joint meeting in Kobe, Japan (and online) at:

• 09:00​–​12:30 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 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]

@reillyeon, would you mind taking this?

[reillyeon]

Progress

What has your spec achieved in the last 12 months?

There has been no progress on this specification in the last year and no implementation changes I am aware of.

Blockers

Is anything preventing it from moving to Rec?

The primary blocker is lack of interest from participants in moving past the current Candidate Recommendation Draft.

The API itself is implemented in a reasonably interoperable fashion in multiple engines with the exception of:

• deviceorientationabsolute – Not available in WebKit-based browsers.
• Automation – Only available in Chromium-based browsers.

Testing

Is there a testing plan for this spec?

The specification includes an Automation section defining Web Driver commands which are used by the web platform tests.

Next Steps

How will you unblock it? Do you need help?

The group needs to build consensus on the Automation interface so that the Web Platform Tests can pass across all implementations.