Intent to Extend Experiment: ServiceWorker static routing API
Shunya Shishido
Contact emails
yyana...@google.com, sisid...@chromium.org
Explainer
https://github.com/WICG/service-worker-static-routing-api
Specification
https://github.com/w3c/ServiceWorker/pull/1686
Summary
This API allows developers to configure the routing, and allows them to offload simple things ServiceWorkers do. If the condition matches, the navigation happens without starting ServiceWorkers or executing JavaScript, which allows web pages to avoid performance penalties due to ServiceWorker interceptions.
Blink component
TAG review
https://github.com/w3ctag/design-reviews/issues/863
TAG review status
Issues addressed
Risks
Interoperability and Compatibility
Gecko: Positive (https://github.com/mozilla/standards-positions/issues/828)
WebKit: No signal. (https://github.com/WebKit/standards-positions/issues/206)
Web developers: Positive (https://github.com/w3c/ServiceWorker/issues/1373) We see many positive signals and feedback from developers on the Github issue and other places (e.g. https://jakearchibald.com/2019/service-worker-declarative-router/#disqus_thread). Also, we have several partners lined up.
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?
Goals for experimentation
The purpose of the experiment and the associated Origin Trial is to gather data on whether this has estimated performance upsides or not. Also, we welcome any feedback, API surface proposals, and suggestions for additional scenarios that this API should support.
Reason this experiment is being extended
The new API shape was discussed based on the community feedback (issue comments). We’d like to have additional milestones to ship the new shape and gather further feedback. Also, we don’t get enough feedback from partners yet as some minor issues had blocked partner OT participation, but now they’re ready to try.
Since the original OT request, we've made progress on TAG review, signals, WPT tests based on the API surface change, public explainer location from the personal Github repo to WICG.
Any risks when the experiment finishes?
No.
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes.
Is this feature fully tested by web-platform-tests?
Yes.
Tracking bug
https://bugs.chromium.org/p/chromium/issues/detail?id=1371756
Launch bug
https://launch.corp.google.com/launch/4261120
Estimated milestones
Links to previous Intent discussions
Intent to Experiment: https://groups.google.com/a/chromium.org/g/blink-dev/c/_H8rqHW9ERQ/m/KLnRZaz3AAAJ
Intent to Prototype:
https://groups.google.com/a/chromium.org/g/blink-dev/c/fyvsde2ay2A/m/RH9E8hB0AgAJ
Link to entry on the feature dashboard
https://chromestatus.com/feature/5185352976826368
Rick Byers
--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGMyg-aXZY75LnphMA6sahG_a63UjKzSxsPiZCXCWMQuvaNBnQ%40mail.gmail.com.