dom...@chromium.org, robe...@chromium.org
https://github.com/WICG/nav-speculation/blob/main/opt-in.md
https://wicg.github.io/nav-speculation/prerendering.html#navigate-fetch-patch
https://docs.google.com/document/d/1WsDYA8NMCSwsK8dXCKdajdAd3ZcQUu9w1eoe0hEB_nU/edit?usp=sharing
Previously we launched same-origin prerendering triggered by the speculation rules API. This expands coverage to also allow triggering same-site cross-origin pages. This prerendering will be done with credentials and storage access, but such prerender targets will need to opt in by using the `Supports-Loading-Mode: credentialed-prerender` header.
https://github.com/w3ctag/design-reviews/issues/721#issuecomment-1235043792
Pending
This feature does not have significant interoperability or compatibility risks on top of the already-shipped same-origin prerendering feature. This is mostly a straightforward extension of that.
The only potentially-interesting questions are around the design of the Supports-Loading-Mode header, which is the main new web-exposed "API". We've designed the header with an eye toward being easily implementable and future-extensible, using the structured headers infrastructure.
Gecko: No signal. No signal on previous requests for prerendering and prefetching. I added a comment to the existing issue about prerendering.
WebKit: No signal. No signal on previous requests for prerendering and prefetching. I took this opportunity to re-file on their new GitHub repository in the hopes of getting some feedback, and there was some brief discussion of the cross-site case, but nothing about the same-site cross-origin case.
Web developers: Positive. We've heard from a few partners that they want to prerender among other same-site origins they own, but cannot yet do so.
This feature is triggered by the speculation rules API: https://chromestatus.com/feature/5740655424831488
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
This feature is not available on WebView.
DevTools support for prerendering in general remains in the early stages; you can track that work in https://crbug.com/1217029, or see our general development guide.
However, this expansion to cross-origin same-site target pages does not have any special debuggability concerns.
No. Prerendering is not supported on Android WebView.
SameSiteCrossOriginForSpeculationRulesPrerender
False
https://bugs.chromium.org/p/chromium/issues/detail?id=1356449
Ship in 109 on both desktop and Android.
None.
https://chromestatus.com/feature/4899735257743360
This intent message was generated by Chrome Platform Status and tweaked by hand.
--
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/b9317f2b-3c20-4a09-833c-13d80cfa672en%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM0wra_-3QntCwmWxNL5FwCH17PPxZno4K-9O%3Dco8vNadF3uoQ%40mail.gmail.com.
LGTM1
--
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/00000000000054925b05ec7e9f06%40google.com.
LGTM3
/Daniel
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw-v1ZsJBV0X_Sw0iEOE%3D%3D3c_JHCdPSyOnnvTZkXSZ5PoA%40mail.gmail.com.