WPT
wpt / webrtc / RTCPeerConnection-connectionState.https.html
Spec: WebRTC ↗
Runs: Chrome 155.0.8039.0 (wpt@6ec9fd59f, 2026-09-03) | Firefox 157.0a1 (wpt@6ec9fd59f, 2026-09-03) | Safari 251 preview (wpt@5ce815a83, 2026-08-27) | Ladybird 1.0-795e1 (wpt@7e3d005d7, 2026-09-03) | Servo Servo 0.6 (wpt@09159dcb3, 2026-09-02) | Blitz 188486089 (wpt@a95401e4e, 2026-09-02)
View on the Blitz WPT dashboard | Open test on wpt.live | wpt.fyi
| Chrome | Firefox | Safari | Ladybird | Servo | Blitz | |
|---|---|---|---|---|---|---|
| Total | 8/8 | 8/8 | 8/8 | 0/8 | 0/8 | NOT RUN |
| Subtest | Chrome | Firefox | Safari | Ladybird | Servo | Blitz |
|---|---|---|---|---|---|---|
| Initial connectionState should be new | PASS | PASS | PASS | FAIL | FAIL | — |
| Closing the connection should set connectionState to closed | PASS | PASS | PASS | FAIL | FAIL | — |
| connection with one data channel should eventually have connected connection state | PASS | PASS | PASS | FAIL | FAIL | — |
| connection with one data channel should eventually have transports in connected state | PASS | PASS | PASS | FAIL | FAIL | — |
| connectionState remains new when not adding remote ice candidates | PASS | PASS | PASS | FAIL | FAIL | — |
| connectionState transitions to connected via connecting | PASS | PASS | PASS | FAIL | FAIL | — |
| when adding a datachannel to an existing unbundled connected PC, it should go through a connecting state | PASS | PASS | PASS | FAIL | FAIL | — |
| Closing a PeerConnection should not fire connectionstatechange event | PASS | PASS | PASS | FAIL | FAIL | — |