Chrome VS Firefox

504 views
Skip to first unread message

Brian Berry

unread,
Aug 30, 2016, 9:03:43 AM8/30/16
to discuss-webrtc
I have a webrtc application that works good in Chrome but I get errors in firefox. The following two warnings are displayed in the Firefox console. What is the difrences between Firefox and chrome. If I change code to get rid of the Firefox warnings then the chrome app doesn't work any longer. How do I make those two work together?

//////******Firefox warnings

RTCIceServer.url is deprecated! Use urls instead. (unknown)

onaddstream is deprecated! Use peerConnection.ontrack instead. (unknown)

navigator.mozGetUserMedia has been replaced by navigator.mediaDevices.getUserMedia

********////////////////

PhistucK

unread,
Aug 30, 2016, 11:34:19 AM8/30/16
to WebRTC-discuss
You should use adapter.js in order to bridge over the differences between the various WebRTC (and even ORTC, for Edge!) implementations. It lets you use the latest W3C standard names and properties, without any prefix.
Some day, they will be completely interoperable, but this is not quite the case today.


☆PhistucK

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrtc+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/dcc13e2f-967e-4359-bf71-36e81dfaddcc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Christoffer Jansson

unread,
Aug 31, 2016, 8:25:21 AM8/31/16
to WebRTC-discuss
Yes please do and contributions are welcome. The more people that are using adapter.js the more scenarios/use cases we can cover.

/Chris

On Tue, Aug 30, 2016 at 5:34 PM PhistucK <phis...@gmail.com> wrote:
You should use adapter.js in order to bridge over the differences between the various WebRTC (and even ORTC, for Edge!) implementations. It lets you use the latest W3C standard names and properties, without any prefix.
Some day, they will be completely interoperable, but this is not quite the case today.


☆PhistucK
On Mon, Aug 29, 2016 at 9:57 PM, Brian Berry <particul...@gmail.com> wrote:
I have a webrtc application that works good in Chrome but I get errors in firefox. The following two warnings are displayed in the Firefox console. What is the difrences between Firefox and chrome. If I change code to get rid of the Firefox warnings then the chrome app doesn't work any longer. How do I make those two work together?

//////******Firefox warnings

RTCIceServer.url is deprecated! Use urls instead. (unknown)

onaddstream is deprecated! Use peerConnection.ontrack instead. (unknown)

navigator.mozGetUserMedia has been replaced by navigator.mediaDevices.getUserMedia

********////////////////

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/dcc13e2f-967e-4359-bf71-36e81dfaddcc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CABc02_%2BPYAXt0A6kaC-A15A%2B33Nd9Er6acvH6nyAfvsNrgbfgA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.
--
/Chris
Reply all
Reply to author
Forward
0 new messages