← back to v149 · disconnect-websockets-on-bfcache-entry

conformance · v149

v149 · disconnect-websockets-on-bfcache-entry — conformance probe

6 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.

browser: spec: https://html.spec.whatwg.org/multipage/web-sockets.html#dom-websocket chromestatus: #5068439115923456 generated 2026-06-01T08:15:14Z by conformance-author-v1-subagent
0
pass
0
fail
0
blocked
6
total
id contract kind verdict detail
websocket-constructor-exists WebSocket is exposed as a global constructor. spec ↗ exists
websocket-close-is-function WebSocket.prototype.close is callable — this is what the UA triggers on BFCache entry. spec ↗ typeof
websocket-closed-state-constant WebSocket.CLOSED is the readyState constant the connection ends in after BFCache eviction. spec ↗ script
pageshow-event-supported window supports the pageshow event whose persisted flag distinguishes BFCache restores. spec ↗ script
pagehide-event-supported window supports the pagehide event used to detect BFCache entry from script. spec ↗ script
page-transition-event-persisted PageTransitionEvent exposes the boolean persisted attribute — true when restored from BFCache. spec ↗ script