Bug 194890
| Summary: | RTCPeerConnection.getSenders(), when called in signalingState "closed" returns an empty array | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Manjesh Malavalli <mmalavalli> |
| Component: | WebRTC | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | bfulgham, webkit-bug-importer, youennf |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari Technology Preview | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Manjesh Malavalli
Steps to reproduce:
1. Run https://jsfiddle.net/j7cx8p23/ in a new tab.
2. Observe the browser console.
Expected behavior:
getSenders() should return a non-empty array of RTCRtpSenders.
Actual behavior:
getSenders() returns an empty array.
NOTE: getSenders() works as expected in Chrome 72 (stable) and Firefox 65 (stable)
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Brent Fulgham
Our behavior does not match Chrome in macOS 13.
Radar WebKit Bug Importer
<rdar://problem/96318585>
youenn fablet
Calling close on a peer connection should stop all transceivers.
Stopped transceivers should not be listed by getSenders/getReceivers.
We are aligned to the spec, as well as Firefox.
I think we should close this radar except if we should revisit the spec.
@Manjesh, is that causing interoperability issues?
Brent Fulgham
Please REOPEN if we have misunderstood your report, or if the spec language changes to match your expectation here.