WPT
wpt / webrtc / RTCRtpParameters-transactionId.html?rest
Spec: WebRTC ↗
Runs: Chrome 155.0.8038.0 (wpt@b1a7025f8, 2026-09-02) | Firefox 157.0a1 (wpt@b1a7025f8, 2026-09-02) | Safari 251 preview (wpt@5ce815a83, 2026-08-27) | Ladybird 1.0-a7884 (wpt@b1a7025f8, 2026-09-02) | Servo Servo 0.6 (wpt@09159dcb3, 2026-09-02) | Blitz 744bf2158 (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 | 3/6 | 6/6 | 3/6 | 0/6 | 0/6 | NOT RUN |
| Subtest | Chrome | Firefox | Safari | Ladybird | Servo | Blitz |
|---|---|---|---|---|---|---|
| sender.getParameters() should return the same transaction ID if called back-to-back without relinquishing the event loop, even if the microtask queue runs | FAIL | PASS | FAIL | FAIL | FAIL | — |
| sender.getParameters() should return the same transaction ID if called back-to-back without relinquishing the event loop, even if there is an intervening call to setParameters | FAIL | PASS | FAIL | FAIL | FAIL | — |
| sender.getParameters() should return a different transaction ID if the event loop is relinquished between multiple calls | PASS | PASS | PASS | FAIL | FAIL | — |
| sender.setParameters() with transaction ID different from last getParameters() should reject with InvalidModificationError | PASS | PASS | PASS | FAIL | FAIL | — |
| setParameters() with parameters older than last getParameters() should reject with InvalidModificationError | PASS | PASS | PASS | FAIL | FAIL | — |
| setParameters() when the event loop has been relinquished since the last getParameters() should reject with InvalidStateError | FAIL | PASS | FAIL | FAIL | FAIL | — |