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 None 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://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EServiceWorker> TAG review https://github.com/w3ctag/design-reviews/issues/958 TAG review status Issues addressed Risks Interoperability and Compatibility The original ServiceWorker static routing API has received positive signals from Firefox <https://github.com/mozilla/standards-positions/issues/828>, WebKit <https://github.com/WebKit/standards-positions/issues/206> and Web developers. We presented these at TPAC 2024 and received no negative feedback, and we have filed for formal signals. There are no compatibility risks, as this proposal only adds new fields to the timing information and will not modify any of the existing fields. 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? None Goals for experimentation The purpose of the experiment and the associated Origin Trial is to gather data on whether this provides enough information on debuggability of the developers. Also, we welcome any feedback, API surface proposals, and suggestions for additional scenarios. Ongoing technical constraints None Debuggability The resource timing info can be checked from devtools panels as well, thus the new feature can also be debugged using the same approach. Workflows such as a new section in the Timing panel in the devtools will help the developers to better understand the behavior of static routing API and its resource timing. 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 chrome://flags None Finch feature name ServiceWorkerStaticRouterTimingInfo Requires code in //chrome? False Tracking bug https://crbug.com/41496865 Estimated milestones Origin trial desktop first 131 Origin trial desktop last 136 Origin trial Android first 131 Origin trial Android last 136 Origin trial WebView first 131 Origin trial WebView last 136 Link to entry on the Chrome Platform Status https://chromestatus.com/feature/6309742380318720?gate=6011323757625344 Links to previous Intent discussions Intent to Prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFXMW906RJCQXui4UHUWukJwXS8kmHpthQFPRWnTkbhcR8D_XA%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/CAFXMW902YSWgaAjhvmJK%2BEwU8DMrW-j8j8MTsr1yKV7di%2Bs3-w%40mail.gmail.com.
