Intent to Implement: Navigation to Bundled Exchanges (Web Packaging)

111 views
Skip to first unread message

Kunihiko Sakamoto

unread,
Sep 10, 2019, 3:05:25 AM9/10/19
to blink-dev, webpack...@chromium.org

Contact emails

Eng: {ksakamoto, horo, toyoshim, kinuko}@chromium.org

PM: kenji...@chromium.org

Spec: jyas...@chromium.org 


Explainer

Web Packaging explainer:

https://github.com/WICG/webpackage/blob/master/explainer.md


Demo Video (offline user sharing of a web page using a custom Chrome build):

https://www.youtube.com/watch?v=rs-3R0ji6dA


Spec/Design doc

Format spec proposal: https://wicg.github.io/webpackage/draft-yasskin-wpack-bundled-exchanges.html


Navigation with Bundled Exchanges explainer:

https://docs.google.com/document/d/1KFmtiE3DHgKfQH5-nKtLiacMrXsoKIXQZ-VIMGHMje0/edit

which will be formalized into Fetch+HTML integration in https://wicg.github.io/webpackage/loading.html.


Navigation to Bundled Exchanges design doc at

https://docs.google.com/document/d/1Bulrd7E1lFZyPfRFIXP3vNMOM9FX-kWJOCxMOeR8pAQ/view#


Tag review: To be filed soon, and will update the intent thread once we do so. 


Summary

Bundled HTTP Exchanges is a format proposal that can represent a collection of HTTP exchanges. An HTTP exchange is a pair of HTTP request/response. It can include signatures with the semantics of Signed HTTP Exchanges, or not. We have previously sent a meta intent for implementing Bundled Exchanges, but it focused more on the behavior outside of web-facing use cases, e.g. pre-install or store-install for PWAs.


This intent is for implementing the navigation logic with Bundled Exchanges, i.e. how a UA can navigate into a page whose entire resources (including main and sub resources) are bundled in a Bundled Exchange. It is expected to enable easy sharing, distribution and offline browsing of web sites and web apps.

Please also see the previous meta intent for more context:

https://groups.google.com/a/chromium.org/d/msg/blink-dev/hVszlf4l2_E/1K_ZgQ4lBQAJ


Risks

Interoperability and Compatibility:
Potentially high as the spec is still at its very early stage. The format spec is designed to be backward compatible so that we can make breaking spec changes.


Edge / Firefox / Safari: No public signals (for Bundled HTTP Exchanges)

Web / Framework developers: hearing interests


Activation

We have a set of Go tools on public github repository for generating and examining Bundled Exchanges. We are also considering providing additional tools written in other languages (e.g. javascript) and available on other platforms.


Debuggability

No special DevTools support is planned at this point, while we may add some in the future.

 

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 feature dashboard

https://www.chromestatus.com/feature/5377722941440000


Requesting approval to ship?

No.


Reply all
Reply to author
Forward
0 new messages