Skip to content

Add new strings for notRestoredReason #11381

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

lozy219
Copy link

@lozy219 lozy219 commented Jun 15, 2025

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 )

@lozy219
Copy link
Author

lozy219 commented Jun 15, 2025

@domenic @smaug---- could you help to review this change? This is an addition to #9360

Copy link
Member

@domenic domenic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants