Re: [w3c/ServiceWorker] TPAC 2025 status report (Issue #1787)

yoshisatoyanagisawa left a comment (w3c/ServiceWorker#1787)

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](https://github.com/w3c/ServiceWorker/pull/1769)). This includes ensuring timingInfo is returned correctly during network fallbacks ([#1772](https://github.com/w3c/ServiceWorker/pull/1772), [#1773](https://github.com/w3c/ServiceWorker/pull/1773), [#1774](https://github.com/w3c/ServiceWorker/pull/1774), [#1777](https://github.com/w3c/ServiceWorker/pull/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](https://github.com/w3c/ServiceWorker/issues/1784)).  
    * Clarified cache access mechanisms, aligning with the Storage specification by using "obtain a local storage bottle map" ([#1786](https://github.com/w3c/ServiceWorker/pull/1786), [#1789](https://github.com/w3c/ServiceWorker/pull/1789)).  
    * Corrected storage key usage for subresource requests within Handle Fetch for cache lookups ([#1790](https://github.com/w3c/ServiceWorker/pull/1790)).  
    * Removed unnecessary global CacheStorage definition ([#1792](https://github.com/w3c/ServiceWorker/pull/1792)).  
  * **Editorial**:  
    * Improved the robustness of fetchController termination checks within fetch handling ([#1780](https://github.com/w3c/ServiceWorker/pull/1780)).  
    * Updated handle fetch algorithm to consider null source ([#1768](https://github.com/w3c/ServiceWorker/pull/1768)).  
    * not should also be mutual exclusive ([#1754](https://github.com/w3c/ServiceWorker/pull/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](https://github.com/w3c/ServiceWorker/pull/1756)).

**Repository Management & Editorial**:

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

**Normative Changes & Alignments**:

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

A full list of merged pull requests can be found [here](https://github.com/w3c/ServiceWorker/pulls?q=is%3Apr+updated%3A%3E2024-08-13+is%3Aclosed).

#### 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](https://github.com/w3c/ServiceWorker/pull/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](https://github.com/w3c/ServiceWorker/pull/1755).  
* Finalizing the updates to module fetching algorithms in [#1658](https://github.com/w3c/ServiceWorker/pull/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](https://github.com/w3c/ServiceWorker/issues?q=is%3Aissue%20state%3Aopen%20label%3ATPAC2025) to reach consensus.  Especially, we focus on the ServiceWorker static routing API ([#1793](https://github.com/w3c/ServiceWorker/issues/1793), [#1796](https://github.com/w3c/ServiceWorker/issues/1796)), multi-thread fetch ([#756](https://github.com/w3c/ServiceWorker/issues/756)), and security issues ([#699](https://github.com/w3c/ServiceWorker/issues/699), [#719](https://github.com/w3c/ServiceWorker/issues/719), [#755](https://github.com/w3c/ServiceWorker/issues/755)).  
* In addition, we may discuss the open PRs ([#1764](https://github.com/w3c/ServiceWorker/pull/1764), [#1757](https://github.com/w3c/ServiceWorker/pull/1757), [#1755](https://github.com/w3c/ServiceWorker/pull/1755), [#1658](https://github.com/w3c/ServiceWorker/pull/1658)) if time allows.

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

Message ID: <w3c/ServiceWorker/issues/1787/3440258319@github.com>