Allow Back/Forward Cache for WebSockets

This policy controls whether active WebSocket connections are disconnected when a page enters back/forward cache. Active WebSocket connections previously prevented a page from being stored in back/forward cache, but Google Chrome has changed this behavior to disconnect the WebSockets instead, allowing the page to be cached and restoring it in a disconnected state.

If this policy is set to Enabled or left unset, WebSockets are disconnected when a page enters back/forward cache.

If this policy is set to Disabled, WebSockets will not be disconnected when a page enters back/forward cache. Since back/forward cache does not support active WebSockets, this means pages with active WebSockets will not be cached.

This policy is intended to be temporary and will be removed in the future.