The back/forward cache stores page state for a fast return. Chrome expanded eligibility for pages with open WebSockets by automatically closing active connections when the page enters the cache.
The demo shows the socket closing as the page is cached, followed by state restoration on Back. An app that needs live updates must handle reconnecting after restoration.
When to use
Check BFCache eligibility and restore handling when Back is slow on a live page.