WebKittens
@annevk
Title of the proposal
Unblock BFCache for pages with active WebSockets by disconnecting on entry.
URL to the spec
whatwg/html#12349 (Draft)
URL to the spec's repository
https://github.com/whatwg/html
Issue Tracker URL
No response
Explainer URL
No response
TAG Design Review URL
No response
Mozilla standards-positions issue URL
mozilla/standards-positions#1390
WebKit Bugzilla URL
No response
Radar URL
No response
Description
This proposal is being discussed in whatwg/html#12085.
Currently, the HTML specification defines active WebSocket connections as a reason to block a page from entering the Back/Forward Cache (BFCache). We propose to allow these pages to be cached by closing any active WebSocket connections upon BFCache entry. This aligns with WebKit's current behavior; we observe that Safari already allows pages with active WebSockets to enter the BFCache by closing the connections upon entry and allowing the page to be restored.
WebKittens
@annevk
Title of the proposal
Unblock BFCache for pages with active WebSockets by disconnecting on entry.
URL to the spec
whatwg/html#12349 (Draft)
URL to the spec's repository
https://github.com/whatwg/html
Issue Tracker URL
No response
Explainer URL
No response
TAG Design Review URL
No response
Mozilla standards-positions issue URL
mozilla/standards-positions#1390
WebKit Bugzilla URL
No response
Radar URL
No response
Description
This proposal is being discussed in whatwg/html#12085.
Currently, the HTML specification defines active WebSocket connections as a reason to block a page from entering the Back/Forward Cache (BFCache). We propose to allow these pages to be cached by closing any active WebSocket connections upon BFCache entry. This aligns with WebKit's current behavior; we observe that Safari already allows pages with active WebSockets to enter the BFCache by closing the connections upon entry and allowing the page to be restored.