Bug 275685
Summary: | [GStreamer][WebRTC] Emit 'track' event before resolving setRemoteDescription's promise | ||
---|---|---|---|
Product: | WebKit | Reporter: | Carlos Bentzen <cadubentzen> |
Component: | WebRTC | Assignee: | Carlos Bentzen <cadubentzen> |
Status: | RESOLVED FIXED | ||
Severity: | Normal | CC: | webkit-bug-importer, youennf |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
See Also: | https://bugs.webkit.org/show_bug.cgi?id=280117 |
Carlos Bentzen
Currently, the GstWebRTC backend emits the 'track' event based on the 'pad-added' signal from webrtcbin.
However, the timing of this signal doesn't conform to https://w3c.github.io/webrtc-pc/#set-description, which mandates that the 'track' event should be emitted right after a remote description is successfully applied. Even before a 'connecting' connectionstatechange event.
Also, because of the above, there's some leftover code in PeerConnectionBackend to handle "pending track events" because of the GstWebRTC backend. We should be able to remove that.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Carlos Bentzen
Pull request: https://github.com/WebKit/WebKit/pull/30038
EWS
Committed 281892@main (584f20310cd3): <https://commits.webkit.org/281892@main>
Reviewed commits have been landed. Closing PR #30038 and removing active labels.
Radar WebKit Bug Importer
<rdar://problem/133299199>