LGTM2 but make sure that all PRs eventually land so they are not left in
limbo.
/Daniel
On 2025-07-18 02:45, Keita Suzuki wrote:
> Are all of the spec PRs for this feature landed? I see some of the
items you linked to are still open.
The ServiceWorker spec has been landed, but the changes on the Fetch
spec and resource timing spec are not landed.
This is because the fetch spec requires "At least two implementers are
interested (and none opposed)", which we are still waiting for.
The resource timing spec has been reviewed, but is waiting for the
fetch spec to be landed.
> Also the spec link for this feature goes to github, not to a
published specification.
Sorry, the spec for SW is this one: https://w3c.github.io/ServiceWorker/
Thanks.
On Thu, Jul 17, 2025 at 1:35 AM Chris Harrelson
<chris...@chromium.org> wrote:
Hi,
Are all of the spec PRs for this feature landed? I see some of the
items you linked to are still open.
Also the spec link for this feature goes to github, not to a
published specification.
On Wed, Jul 16, 2025 at 9:22 AM Alex Russell
<slightly...@chromium.org> wrote:
Thanks for the helpful OT summary doc. LGTM1.
On Monday, July 14, 2025 at 10:47:40 PM UTC-7 Keita Suzuki wrote:
Contact emails
suzukike...@chromium.org, yyanagis...@chromium.org
Explainer
https://github.com/WICG/service-worker-static-routing-api/blob/main/resource-timing-api.md
Specification
https://github.com/w3c/ServiceWorker
Other changes:
https://github.com/w3c/resource-timing/pull/415
https://github.com/whatwg/fetch/pull/1832
Summary
Adds timing information for ServiceWorker Static routing
API, exposed in navigation timing API and resource timing
API for developer use. Service Worker provides timing
information to mark certain points in time. We add two
Static routing API-relevant timing information:
RouterEvaluationStart, time to start matching a request
with registered router rules, and CacheLookupStart, time
to start looking up the cache storage if the source is
"cache". In addition, we also add two router source
information, the matched router source and the final
router source.
Blink component
Blink>ServiceWorker
<https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EServiceWorker%22>
TAG review
https://github.com/w3ctag/design-reviews/issues/958
TAG review status
Issues addressed
Origin Trial Name
Timing Info for ServiceWorker static routing API
Chromium Trial Name
ServiceWorkerStaticRouterTimingInfo
Link to origin trial feedback summary
https://docs.google.com/document/d/19wTiP9sHibJam-XlEV06-jrwSz0M2IKSB-0zqORgYDA/edit?tab=t.0#heading=h.53acks0nurd
Origin Trial documentation link
https://github.com/WICG/service-worker-static-routing-api/blob/main/resource-timing-api.md
WebFeature UseCounter name
kV8PerformanceResourceTiming_WorkerRouterEvaluationStart_AttributeGetter
Risks
Interoperability and Compatibility
None
/Gecko/: No signal
(https://github.com/mozilla/standards-positions/issues/1031)
/WebKit/: No signal
(https://github.com/WebKit/standards-positions/issues/354)
/Web developers/: No signals
/Other signals/:
WebView application risks
Does this intent deprecate or change behavior of existing
APIs, such that it has potentially high risk for Android
WebView-based applications?
Non that I am aware of
Debuggability
None
Will this feature be supported on all six Blink
platforms (Windows, Mac, Linux, ChromeOS, Android,
and Android WebView)?
Yes
Is this feature fully tested by web-platform-tests
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?
Yes
https://wpt.fyi/results/service-workers/service-worker/tentative/static-router/static-router-resource-timing.https.html?label=experimental&label=master&aligned
<https://wpt.fyi/results/service-workers/service-worker/tentative/static-router/static-router-resource-timing.https.html?label=experimental&label=master&aligned>
Flag name on about://flags
None
Finch feature name
ServiceWorkerStaticRouterTimingInfo
Rollout plan
Will ship enabled for all users
Requires code in //chrome?
False
Tracking bug
https://crbug.com/41496865
Availability expectation
Feature will eventually be available on Web Platform
mainline, as it is the part of an already used resource
timing API, and the ServiceWorker static routing API is
already standardized.
Non-OSS dependencies
Does the feature depend on any code or APIs outside the
Chromium open source repository and its open-source
dependencies to function?
n/a
Estimated milestones
Shipping on desktop 140
Origin trial desktop first 131
Origin trial desktop last 136
Origin trial extension 1 end milestone 139
Shipping on Android 140
Origin trial Android first 131
Origin trial Android last 136
Origin trial WebView first 131
Origin trial WebView last 136
Anticipated spec changes
Open questions about a feature may be a source of future
web compat or interop issues. Please list open issues
(e.g. links to known github issues in the project for the
feature specification) whose resolution may introduce web
compat/interop risk (e.g., changing to naming or structure
of the API in a non-backward-compatible way).
We are making changes to the following specs:
- Service Worker Spec
https://github.com/w3c/ServiceWorker/pull/1769 has already
been merged
- Resource timing spec
https://github.com/w3c/resource-timing/pull/415 has been
reviewed, and are waiting for merge (waiting for the
fetch-spec changes to be reviewed)
- Fetch Spec https://github.com/whatwg/fetch/pull/1832 has
been reviewed, but are still waiting for editor's review
and are also waiting for other vendor's signal.
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/6309742380318720?gate=6038764639223808
Links to previous Intent discussions
Intent to Prototype:
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFXMW906RJCQXui4UHUWukJwXS8kmHpthQFPRWnTkbhcR8D_XA%40mail.gmail.com
Intent to Experiment:
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFXMW902YSWgaAjhvmJK%2BEwU8DMrW-j8j8MTsr1yKV7di%2Bs3-w%40mail.gmail.com
Intent to Extend Experiment 1:
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFXMW933udcB3e_OHTL-TjcD5G1bFGL88XAsY537h93eCfBPFQ%40mail.gmail.com
This intent message was generated by Chrome Platform
Status <https://chromestatus.com/>.
--
You received this message because you are subscribed to the
Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to blink-dev+unsubscr...@chromium.org.
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/3ec0a1a2-706b-4186-b759-4bd7569a53a9n%40chromium.org
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/3ec0a1a2-706b-4186-b759-4bd7569a53a9n%40chromium.org?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google
Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to blink-dev+unsubscr...@chromium.org.
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFXMW93t0MZgjTtTmBNNV2ko-DW9-9rrRjJy%3DyWr2Ps0oHZt0Q%40mail.gmail.com
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFXMW93t0MZgjTtTmBNNV2ko-DW9-9rrRjJy%3DyWr2Ps0oHZt0Q%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-dev+unsubscr...@chromium.org.
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/eb99f488-1d10-4e92-ac18-cec5637862c0%40gmail.com.
