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 advancing beyond CR?
  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.

[yoshisatoyanagisawa]

Thanks @monica-ch for reviewing the report before the post!

Here is a summary of the ServiceWorker specification's progress over the last 12 months, blockers, testing status, and next steps.

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

The ServiceWorker specification has seen significant activity in the past year, with a focus on refining existing features, improving integration with other specifications, and editorial enhancements.

Key Feature Updates:

• Service Worker Static Routing API
  • Resource Timing: Added new fields and getter steps for resource timing information related to static routes, to be exposed via the Resource Timing API (#1769). This includes ensuring timingInfo is returned correctly during network fallbacks (#1772, #1773, #1774, #1777).
  • Cache handling: A confusing and conceptually flawed phrase, "the registration's storage key's name to cache map," has been revised (filed as #1784).
    • Clarified cache access mechanisms, aligning with the Storage specification by using "obtain a local storage bottle map" (#1786, #1789).
    • Corrected storage key usage for subresource requests within Handle Fetch for cache lookups (#1790).
    • Removed unnecessary global CacheStorage definition (#1792).
  • Editorial:
    • Improved the robustness of fetchController termination checks within fetch handling (#1780).
    • Updated handle fetch algorithm to consider null source (#1768).
    • not should also be mutual exclusive (#1754).
• Service Worker Auto Preload: Introduced an optional browser optimization to minimize navigation bootstrap cost by dispatching network requests before worker start-up. Developers can opt-out using the ServiceWorker Static Routing API (#1756).

Repository Management & Editorial:

• The ServiceWorker editors have changed (#1750).
• The ServiceWorker specification repository was officially moved under the umbrella of the WebApps Working Group (#1759).
  • We are also working on making the ServiceWorker specification publication automatic (#1758).
• Specification files were reorganized to the root directory for better maintainability (#1794).
• Workflow has been updated to fix the CI errors (#1745).
• Numerous editorial fixes were made to improve clarity, fix typos, and ensure spec consistency, including link fixes, bikeshed warning corrections, and refactoring (#1729, #1753, #1760, #1766, #1778).

Normative Changes & Alignments:

• Corrected ServiceWorkerRegistration Web IDL to reflect that update() returns a Promise, aligning the spec with existing browser implementations (#1767).
• Added the "cross site ancestry" field to environment settings objects to align with HTML and Fetch for SameSite cookie behavior (#1775).
• Updated QuotaExceededError usage to align with its graduation to a new error class in Web IDL (#1782).

A full list of merged pull requests can be found here.

ii. Blockers - Is anything preventing it from advancing beyond CR?

• While significant progress has been made, ensuring cross-browser implementation and interoperability for newer features like the Static Routing API and Auto Preload remains key.
• Open pull requests such as #1757 (no-cors handling in the SW static routing) need resolution.
• Further discussion and consensus may be needed on the best approaches for task queuing and parallel execution as raised in #1755.
• Finalizing the updates to module fetching algorithms in #1658.

iii. Testing - Is there a testing plan for this spec?

• Web Platform Tests (WPT) are actively developed for new features and to cover existing functionality.
• Contributions to improve test coverage are always welcome, particularly for the Service Worker Static Routing API and its interaction with other parts of the platform.

iv. Next Steps - How will you unblock it? Do you need help?

• TPAC Discussions: We propose discussing the open issues with the TPAC2025 tag to reach consensus. Especially, we focus on the ServiceWorker static routing API (#1793, #1796), multi-thread fetch (#756), and security issues (#699, #719, #755).
• In addition, we may discuss the open PRs (#1764, #1757, #1755, #1658) if time allows.