Closed Bug 1657394 Opened 4 years ago Closed 4 years ago

Bundle-only transceivers do not have a transport in have-local-offer

Categories

(Core :: WebRTC: Signaling, defect, P2)

defect

Tracking

()

RESOLVED FIXED
82 Branch
Tracking Status
firefox82 --- fixed

People

(Reporter: bwc, Assigned: bwc)

References

Details

Attachments

(4 files)

Discovered over in bug 1654399.

https://phabricator.services.mozilla.com/D84460#inline-487771

We need to fix this so we can have an RTCDtlsTransport in have-local-offer.

Seeing a failure in RTCPeerConnection-createDataChannel.html on opt builds only...

Ok, finding a number of corner-cases that we don't get quite right as the answerer when the bundle-tag is disabled (particularly, when there is another m-section with a transport besides the bundle-tag). This might be a little bit more involved than I expected.

Try looks good.

Pushed by bcampen@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/fa9ee4466bf5
Test-case for bug. r=mjf
https://hg.mozilla.org/integration/autoland/rev/5470a86abcf9
Make sure transports are set up in have-local-offer. r=mjf
https://hg.mozilla.org/integration/autoland/rev/d44e6fa4c00d
Test for cases where we have a fallback bundle transport. r=mjf
https://hg.mozilla.org/integration/autoland/rev/45ac7058b50a
When generating an answer, if the bundle transport is disabled, try to fall back to a suitable alternative when one is available. r=mjf
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/25249 for changes under testing/web-platform/tests
Upstream PR merged by moz-wptsync-bot
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: