Closed Bug 1840555 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 40764 - Add more RTP header extension wpt

Categories

(Core :: WebRTC, task, P4)

task

Tracking

()

RESOLVED FIXED
117 Branch
Tracking Status
firefox117 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 40764 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/40764
Details from upstream follow.

Philipp Hancke <phancke@microsoft.com> wrote:

Add more RTP header extension wpt

BUG=chromium:1051821

Change-Id: I4ac1937cd7e4fbcb41280d1f5a2853d02e497825
Reviewed-on: https://chromium-review.googlesource.com/4648130
WPT-Export-Revision: 71cb647ba0477e30969dc48b9721df2b1ce09286

Component: web-platform-tests → WebRTC
Product: Testing → Core

CI Results

Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 1 tests and 18 subtests

Status Summary

Firefox

OK : 1
FAIL: 18

Chrome

OK : 1
PASS: 18

Safari

OK : 1
FAIL: 18

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

  • /webrtc-extensions/RTCRtpTransceiver-headerExtensionControl.html [wpt.fyi]
    • the audio transceiver.getHeaderExtensionsToNegotiate() includes mandatory extensions: FAIL (Chrome: PASS, Safari: FAIL)
    • the video transceiver.getHeaderExtensionsToNegotiate() includes mandatory extensions: FAIL (Chrome: PASS, Safari: FAIL)
    • setHeaderExtensionsToNegotiate throws TypeError on encountering missing URI: FAIL (Chrome: PASS, Safari: FAIL)
    • setHeaderExtensionsToNegotiate throws TypeError on encountering missing direction: FAIL (Chrome: PASS, Safari: FAIL)
    • setHeaderExtensionsToNegotiate throws InvalidModificationError on encountering unknown URI: FAIL (Chrome: PASS, Safari: FAIL)
    • setHeaderExtensionsToNegotiate throws InvalidModificationError when removing elements from the list: FAIL (Chrome: PASS, Safari: FAIL)
    • setHeaderExtensionsToNegotiate throws InvalidModificationError when adding elements to the list: FAIL (Chrome: PASS, Safari: FAIL)
    • setHeaderExtensionsToNegotiate throws InvalidModificationError when setting a mandatory header extension's direction to something else than "sendrecv": FAIL (Chrome: PASS, Safari: FAIL)
    • modified direction set by setHeaderExtensionsToNegotiate is visible in subsequent getHeaderExtensionsToNegotiate: FAIL (Chrome: PASS, Safari: FAIL)
    • Unstopped extensions turn up in offer: FAIL (Chrome: PASS, Safari: FAIL)
    • Stopped extensions do not turn up in offers: FAIL (Chrome: PASS, Safari: FAIL)
    • The set of negotiated extensions has the same size as the set of extensions to negotiate: FAIL (Chrome: PASS, Safari: FAIL)
    • Header extensions can be reactivated in subsequent offers: FAIL (Chrome: PASS, Safari: FAIL)
    • Header extensions can be deactivated on a per-mline basis: FAIL (Chrome: PASS, Safari: FAIL)
    • Extensions not negotiated by the peer are stopped in getNegotiatedHeaderExtensions: FAIL (Chrome: PASS, Safari: FAIL)
    • Prior to negotiation, getNegotiatedHeaderExtensions() returns stopped for all extensions.: FAIL (Chrome: PASS, Safari: FAIL)
    • Answer header extensions are a subset of the offered header extensions: FAIL (Chrome: PASS, Safari: FAIL)
    • A subsequent offer from the other side will reoffer extensions not negotiated by the initial offerer: FAIL (Chrome: PASS, Safari: FAIL)
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/3547534b1170 [wpt PR 40764] - Add more RTP header extension wpt, a=testonly
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 117 Branch
You need to log in before you can comment on or make changes to this bug.