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.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
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.
N/A
The registered router rules are visible via chrome://serviceworker-internals. We’re also considering showing the same info in DevTools. crbug.com/1467701
OriginTrial desktop last | 121 |
OriginTrial desktop first | 116 |
OriginTrial Android last | 121 |
OriginTrial Android first | 116 |
OriginTrial webView last | 121 |
OriginTrial webView first | 116 |
--
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-abNsH2mfBw3%2BiaJgMn3SKCEzBzw0FuMudbmQ9XhkjEVg%40mail.gmail.com.
LGTM!On Tue, Jul 25, 2023 at 8:44 PM Shunya Shishido <sisid...@chromium.org> wrote:
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.