Closed
Bug 1624017
Opened 5 years ago
Closed 4 years ago
Firefox using only mDNS candidates for google meet
Categories
(Core :: WebRTC: Networking, defect, P3)
Core
WebRTC: Networking
Tracking
()
RESOLVED
DUPLICATE
of bug 1238249
People
(Reporter: bwc, Unassigned)
Details
This is because meet is carrying out offer/answer before gUM, and we do not expand our gathered candidates when gUM is granted.
|
Reporter | |
Comment 1•5 years ago
|
||
This doesn't prevent meet from working, since their conferencing server can learn prflx candidates for us.
|
||
Updated•5 years ago
|
|
|
Reporter | |
Comment 2•4 years ago
|
||
So, I think this isn't really an mDNS problem. This would probably be better classified as a dupe of bug 1238249, since that would allow us to continue gathering candidates once gUM happens.
No longer blocks: 1544770
Severity: normal → S3
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•