Contact emailskenjibah...@chromium.org, fer...@chromium.org, denom...@chromium.org, le...@chromium.org
Specification https://github.com/fergald/explainer-bfcache-ccns/blob/main/README.md Design docs https://docs.google.com/document/d/1qX1w6L6laTzpFTh78dvT7wwC1060Z3he2Azp4BAwsUE/edit?usp=sharing https://github.com/fergald/explainer-bfcache-ccns/blob/main/README.md Summary A behavior change to safely store (and restore) pages in the Back/Forward Cache despite the presence of a "Cache-control: no-store" HTTP header on HTTPS pages. This would allow pages to enter BFCache and be restored as long as there are no changes to cookies or to RPCs using the `Authorization:` header. Blink componentUI>Browser>Navigation>BFCache <https://bugs.chromium.org/p/chromium/issues/list?q=component:UI%3EBrowser%3ENavigation%3EBFCache> Search tagsbfcache <https://chromestatus.com/features#tags:bfcache> TAG review TAG review statusNot applicable Risks Interoperability and Compatibility *Gecko*: No signal *WebKit*: No signal *Web developers*: No signals *Other signals*: WebView application risks Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? None Debuggability Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?No BFCache is not supported on WebView, so this change has no impact there. Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> ?No Flag name on chrome://flags Finch feature nameCacheControlNoStoreEnterBackForwardCache Requires code in //chrome?False Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1228611 Launch bughttps://launch.corp.google.com/launch/4251651 Estimated milestones DevTrial on desktop 116 DevTrial on Android 116 Anticipated spec changes Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way). None Link to entry on the Chrome Platform Status https://chromestatus.com/feature/6705326844805120 Links to previous Intent discussions This intent message was generated by Chrome Platform Status <https://chromestatus.com/>. -- 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+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAN_fHtkLz7t6rZCdvCyFcyC3%3D-51DZGjgGkGJ6JSGoLmkGV-jg%40mail.gmail.com.
