Intent to Experiment: Subresource loading with Web Bundles
Hayato Ito
Contact emails
hay...@chromium.org, ho...@chromium.org, ksak...@chromium.org, deno...@google.com
Spec
https://github.com/WICG/webpackage/blob/master/explainers/subresource-loading.md
There is not yet a specification integrating bundles into HTML.
Summary
Provides a new approach to load a large number of resources efficiently using a format that allows multiple resources to be bundled, e.g. Web Bundles.
Link to “Intent to Prototype” blink-dev discussion
https://groups.google.com/a/chromium.org/g/blink-dev/c/wYn13HabRN0/m/L4y4iY1-AgAJ
TAG review
https://github.com/w3ctag/design-reviews/issues/616
Goals for experimentation
There are three main goals:
Measure how this feature makes a subresource loading faster in real sites.
Measure how this feature improves Ad Serving. See WebBundles for Ad Serving for details.
Collect feedback on the API surface so that we can discuss how this and alternative approaches like resource-bundles could potentially converge in the future.
Experiment timeline
M90-M92
Any risks when the experiment finishes?
There is no risk as long as a site uses feature detection using HTMLLinkElement.relList.
Ongoing technical constraints
None.
Debuggability
Developers can know a failed subresource loading from Web Bundles in DevTools's console. We probably need more DevTools debugging support to provide a good debugging experience. Experiments will give us a better change of designing the right support. A related issue is https://crbug.com/1182537.
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes
Link to entry on the Chrome Platform Status
https://www.chromestatus.com/feature/5710618575241216
