Add new strings for notRestoredReason #11381
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As part of the project that enables pages with Cache-control: not store header, we will evict the BFCache-eligible page if it has ever used WebSocket, WebRTC and WebTransport. These are implemented, but the not restore reason string was not specified. Currently Chromium shares the string with the ones used for active WebSocket/WebRTC/WebTransport, but it could be confusing. We are proposing to create 3 new strings for the reason introduced by the CCNS changes.
see https://github.com/fergald/explainer-bfcache-ccns/blob/main/README.md for more information.
(See WHATWG Working Mode: Changes for more details.)
/nav-history-apis.html ( diff )