Google's browser, Chrome obsession for speed remains insatiable as the team has embarked on introducing new specifications that would enable smoother transitions between web pages.

While the new specifications include Web Package, which offer fast loading for the web pages, and Portals, to allow multi-page sites to act as single-page applications through the level of web transitions.

These standards are built on the model of the Accelerated Mobile Pages (AMP) library for web pages to load quickly, especially for mobile devices. And Signed HTTP Exchanges (SXG), a subset of Web Packages, would allow publishers to sign a single HTTP exchange so that the signed exchange can be served from a caching server.

The browser will load the signed exchange, with the publisher’s URL shown in the address bar as the signature in the exchange is proof that the content is from the publisher’s origin.

The Web Packaging gives the browser proof of origin for resources rendered, and with Signed HTTP Exchanges, if a package is signed with a key corresponding to the domain, would be delivered as coming from the domain.

And the Portals proposal would allow a page show another page as an inset and provide smooth transition between inset state and a navigated state from a page showing a portal-aware address as inset and between pages of portal-aware web pages.

The proposal is still in early developmental stages, and the SXG experiment will commence with Chrome 71 browser planned for December release.

Chrome Team working on Specifications to enable faster Transition between Web pages



Google's browser, Chrome obsession for speed remains insatiable as the team has embarked on introducing new specifications that would enable smoother transitions between web pages.

While the new specifications include Web Package, which offer fast loading for the web pages, and Portals, to allow multi-page sites to act as single-page applications through the level of web transitions.

These standards are built on the model of the Accelerated Mobile Pages (AMP) library for web pages to load quickly, especially for mobile devices. And Signed HTTP Exchanges (SXG), a subset of Web Packages, would allow publishers to sign a single HTTP exchange so that the signed exchange can be served from a caching server.

The browser will load the signed exchange, with the publisher’s URL shown in the address bar as the signature in the exchange is proof that the content is from the publisher’s origin.

The Web Packaging gives the browser proof of origin for resources rendered, and with Signed HTTP Exchanges, if a package is signed with a key corresponding to the domain, would be delivered as coming from the domain.

And the Portals proposal would allow a page show another page as an inset and provide smooth transition between inset state and a navigated state from a page showing a portal-aware address as inset and between pages of portal-aware web pages.

The proposal is still in early developmental stages, and the SXG experiment will commence with Chrome 71 browser planned for December release.

No comments