Closed
Bug 1526039
Opened 5 years ago
Closed 5 years ago
about:webrtc is missing protocol in candidates table
Categories
(Core :: WebRTC: Signaling, defect, P2)
Core
WebRTC: Signaling
Tracking
()
RESOLVED
FIXED
mozilla70
People
(Reporter: drno, Assigned: ralderete)
Details
(Keywords: regression)
Attachments
(1 file)
about:webrtc in the ICE stats table no longer is missing the protocol for each of the candidates and shows 'undefined' instead. E.g.
10.252.27.109:59617/undefined(host)
In the Raw candidates section the protocol still shows up.
|
Reporter | |
Updated•5 years ago
|
status-firefox65:
--- → affected
status-firefox66:
--- → affected
status-firefox67:
--- → affected
Keywords: regression
Priority: -- → P2
|
||
Updated•5 years ago
|
|
||
Comment 1•5 years ago
|
||
Unlikely that we need this for 66
|
||
Updated•5 years ago
|
|
||
Updated•5 years ago
|
|
Assignee | |
Comment 2•5 years ago
|
||
"transport" is the old name for the field. This makes it so that the transport
protocol is no longer printed as "undefined" in the ICE candidate table.
|
||
Updated•5 years ago
|
Assignee: nobody → ralderete
Status: NEW → ASSIGNED
Pushed by nohlmeier@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1de6425af33d Fix protocol field in about:webrtc candidates table r=dminor
|
||
Comment 4•5 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox70:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
|
||
Comment 5•5 years ago
|
||
Since the status are different for nightly and release, what's the status for beta?
For more information, please visit auto_nag documentation.
status-firefox69:
--- → ?
|
|
||
Comment 6•5 years ago
|
||
I guess this can ride to 70, but feel free to request uplift if you think this is worth getting in 69.
|
|
||
Updated•5 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•