regression: Kurento Loopback with recording using generators not working
Categories
(Web Compatibility :: Site Reports, defect, P3)
Tracking
(firefox-esr60 unaffected, firefox-esr68 wontfix, firefox68 wontfix, firefox69+ wontfix, firefox70- wontfix, firefox71 wontfix)
People
(Reporter: yoasif, Unassigned)
Details
As reported initially on https://www.reddit.com/r/firefox/comments/co98ef/kurento_fails_on_ubuntu_1804_firefox_68/
STR:
- Navigate to: https://houselannister.vyou.ch/
- Click "Start"
- Give permissions to site for camera
What happens:
Console output on page says:
Error: Error adding candidate
Error: Error adding candidate
TypeError: arguments.unshift is not a function
Video does not appear on remote stream.
Expected result:
Video appears on remote stream, no errors in console.
17:58.27 INFO: No more inbound revisions, bisection finished.
17:58.27 INFO: Last good revision: 2ae5ad0cc2e26e35d3a3c0827f8ac54b8d16be83
17:58.27 INFO: First bad revision: 4cfdc4abb3f01714861097b093c6b65d27ef6074
17:58.27 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=2ae5ad0cc2e26e35d3a3c0827f8ac54b8d16be83&tochange=4cfdc4abb3f01714861097b093c6b65d27ef6074
Reporter | ||
Comment 1•5 years ago
|
||
Byron, can you look into this? Your commit caused this regression. Thanks!
Reporter | ||
Comment 2•5 years ago
|
||
[Tracking Requested - why for this release]:
Regression in WebRTC affecting public sites.
Comment 3•5 years ago
|
||
It just looks like whatever remote endpoint Kurento is using doesn't support the latest ICE candidate signaling from the spec.
Reporter | ||
Comment 4•5 years ago
|
||
Isn't this a webcompat issue? Shouldn't it at least be filed as needs contact or something?
Reporter | ||
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Comment 5•5 years ago
|
||
(In reply to Byron Campen [:bwc] from comment #3)
It just looks like whatever remote endpoint Kurento is using doesn't support the latest ICE candidate signaling from the spec.
Are we not concerned about this working in Chrome and no longer in Firefox? Or will Chrome break this soon, do you know Byron?
Comment 6•5 years ago
|
||
(In reply to Mike Taylor [:miketaylr] from comment #5)
(In reply to Byron Campen [:bwc] from comment #3)
It just looks like whatever remote endpoint Kurento is using doesn't support the latest ICE candidate signaling from the spec.
Are we not concerned about this working in Chrome and no longer in Firefox? Or will Chrome break this soon, do you know Byron?
Kurento should not be treating this as a fatal error anyway. We're signaling additional information in a manner it doesn't support yet, that it could be ignoring. Kurento needs to update their code. I suppose if this continues to be a problem, we can disable these new onicecandidate events until the implementation community catches up.
Comment 7•5 years ago
|
||
Too late for 69 at this point with RC coming next week.
Comment 8•5 years ago
|
||
(Not sure if we should track this if it relies on the site to update code.)
Comment 9•5 years ago
|
||
Untracking since this is an external issue.
Comment 10•4 years ago
|
||
This is "working" the same way in Safari, Firefox and Chrome.
For example in Chrome.
WebSocket connection to 'wss://houselannister.vyou.ch:8433/kurento' failed: Error in connection establishment: net::ERR_SSL_OBSOLETE_VERSION
Updated•4 years ago
|
Description
•