Open jonas0616 opened 7 years ago
Thanks for letting me know, I'll try take a look at this soon. I should probably try it out in the Safari preview as well!
Started looking into this and you're right: the status of RTC Data Channels in Edge is currently only "Under Consideration" (at low priority :-/) whereas the core of WebRTC is supported.
It's looking my Win10 netbook needs some extra help to get updated to a newer Edge, but once that's in place I can start looking into alternative logic.
@jonas0616 You said you have "Microsoft Edge 40.15063.0.0" — is that on a beta channel or something?
I think I managed to get all available (normal) updates for my Win10 netbook but still had a much lower Edge version.
@natevw It looks like Microsoft does not push the update for all machines. According to Windows Experience Blog, it rolls out across the world in phases
, starting with newer machines first.
Hmm, I noticed yesterday that MS actually has some Edge VMs for download: https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/
However, these are the two relevant options:
…so unless I'm missing something with the version numbers, both the stable and "preview" options are way old and maybe not useful here.
@natevw I guess the version you mentioned is EdgeHTML
version.
My Edge version in About this app
shows:
Microsoft Edge 40.15063.0.0
Microsoft EdgeHTML 15.15063
The detailed mapping can be found in Wikipedia
@jonas0616 Ah, excellent! So these should be an even handier debugging aid.
Any word on alternative logic?
it looks like working in latest Edge version 18.***
Oh cool, maybe procrastination paid off then…?
Normally, when the browser does not support WebRTC, ipcalf shows
Nevertheless, Edge only shows
-
in net.ipcalf.com. And the console shows the following error:It looks like there is
webkitRTCPeerConnection
in Edge, but there is nocreateDataChannel
in itswebkitRTCPeerConnection
Version