WebRTC - WebRTC v1.0 API
Real-time communication in the browser. See also "Web RTC - Object RTC API".
http://docs.webplatform.org/wiki/apis/webrtc
http://dev.w3.org/2011/webrtc/editor/webrtc.html
![Jonathan Sampson [MSFT]](https://secure.gravatar.com/avatar/d7d887f36f0d23091cac37c6e7cb1ae4?size=40&default=https://assets1.uvcdn.com/pkg/admin/icons/user_70-62136f6de7efc58cc79dabcfed799c01.png){kind=icon}
Jonathan Sampson [MSFT]
shared this idea
WebRTC is included in Edge 15, which shipped today (11th April) with Windows 10 Creators Update.
22 comments
-
Mark Veenstra
commented
https://test.webrtc.org/ fails with Edge 15. Do you have any blog post or any other information where we need to look into or take account for?
-
Emiliano Magliocca commented
Why is this completed? doesn't work on mobile and xbox one!
-
Feross Aboukhadijeh commented
Does this include WebRTC Data Channel?
-
pongphaga2@hotmail.com
commented
Unfortunately, Internet Explorer doesn't support our new video-calling feature yet. To make a call, open Facebook in Google Chrome or Mozilla Firefox.
-
Maciej “Nux” Jaros
commented
RTCDataChannel is not supported. When will this be implemented?
-
Tim Mensch
commented
A SHIM? David Storey is saying we need to use a SHIM to get WebRTC support?
You seriously consider this a "WE HEAR YA!" close?! This is completely bogus.
If someone can write a shim to make ORTC work, then include it in Edge. This is a marketing response; you're clearly not listening to users if you close a feature request with "NO, USE OUR FEATURE INSTEAD! IT'S COOLER!"
-
Anonymous
commented
Lets be clear: WebRTC as it is implemented now in Chrome, Firefox and Opera is NOT, I repeat NOT, going to be supported. That is what you are saying isn't it?
-
![David Storey [MSFT]](https://secure.gravatar.com/avatar/a38afdf9896a43bfa5595b4bf2a07c1b?size=40&default=https://assets1.uvcdn.com/pkg/admin/icons/user_70-62136f6de7efc58cc79dabcfed799c01.png)
David Storey [MSFT]
commented
There is an adapter to make Chrome, Opera, Firefox, and MS Edge interoperable with a simplified developer friendly API developed by our friends at &yet. Please see https://dev.modern.ie/testdrive/demos/simplewebrtc/ for a demonstration.
-
Lewis Phạm
commented
Why do we even bother supporting Edge since they don't listen to us? 2% market share is nothing.
-
Andrew Beaven
commented
Quick, close the voting so it doesn't become even more obvious that developers want WebRTC over ORTC.
-
Sylvain
commented
Please keep in mind to make something that works for developers.
-
LucasBC
commented
"We hear ya!" Huh? Seriously? Hardly anyone is voting for "ORTC". Stick to the standard the other more popular browsers are supporting.
-
Anonymous
commented
Funny how the post by the IE admin starts with WE HEAR YA! When the overwhelming sentiment is that no... you don't hear us. WebRTC is needed now, not later. There is no reason why you would not implement WebRTC 1.0 then expand into WebRTC 1.1. You are pushing users away from your platform with this kind of move, and featuring yourself into irrelevance. Specially since there are other alternatives that work right now
-
David Storey [MSFT]
commented
Related to this, ORTC is now under active development https://status.modern.ie/webrtcobjectrtcapi?term=rtc
-
former MCP
commented
Is it funny, sad, or scary how only browsers shipped by major content owners refuse to implement a great idea like WebRTC?
-
Anonymous
commented
WebRTC v1.0 is ****.
-
Troy
commented
There is no reason to use IE.
-
Anonymous
commented
They're not going to implement it - it's a direct rival to Skype.
-
gtk2k commented
Confusing and also, there is, because there is also a possibility to vote and think ORTC,
--See Also "Web RTC - Object RTC API" .--
I want you to delete the statement. -
Steve Lee
commented
having 2 standards doesn't help anyone