Thanks for the helpful OT summary doc. LGTM1. On Monday, July 14, 2025 at 10:47:40 PM UTC-7 Keita Suzuki wrote:
> Contact emailssuzukike...@chromium.org, yyanagis...@chromium.org > > Explainer > https://github.com/WICG/service-worker-static-routing-api/blob/main/resource-timing-api.md > > Specificationhttps://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 componentBlink>ServiceWorker > <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EServiceWorker%22> > > TAG reviewhttps://github.com/w3ctag/design-reviews/issues/958 > > TAG review statusIssues addressed > > Origin Trial NameTiming Info for ServiceWorker static routing API > > Chromium Trial NameServiceWorkerStaticRouterTimingInfo > > 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 > > > Flag name on about://flagsNone > > Finch feature nameServiceWorkerStaticRouterTimingInfo > > Rollout planWill ship enabled for all users > > Requires code in //chrome?False > > Tracking bughttps://crbug.com/41496865 > > Availability expectationFeature 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 discussionsIntent 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.
