Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Method 'createDataChannel' not found in Microsoft Edge #1

Open
jonas0616 opened this issue Jun 20, 2017 · 10 comments
Open

Method 'createDataChannel' not found in Microsoft Edge #1

jonas0616 opened this issue Jun 20, 2017 · 10 comments

Comments

@jonas0616
Copy link

jonas0616 commented Jun 20, 2017

Normally, when the browser does not support WebRTC, ipcalf shows

ifconfig | grep inet | grep -v inet6 | cut -d" " -f2 | tail -n1

Nevertheless, Edge only shows - in net.ipcalf.com.
And the console shows the following error:

SCRIPT438: Object doesn't support property or method 'createDataChannel'
net.ipcalf.com (18,9)

It looks like there is webkitRTCPeerConnection in Edge, but there is no createDataChannel in its webkitRTCPeerConnection

Version

Microsoft Edge 40.15063.0.0
@natevw
Copy link
Owner

natevw commented Jun 20, 2017

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!

@natevw
Copy link
Owner

natevw commented Jun 22, 2017

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.

@natevw
Copy link
Owner

natevw commented Aug 16, 2017

@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.

@jonas0616
Copy link
Author

@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.

@natevw
Copy link
Owner

natevw commented Sep 21, 2017

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:

  • MSEdge on Win10 (x64) Stable (15.15063)
  • MSEdge on Win10 (x64) Preview (16.16257)

…so unless I'm missing something with the version numbers, both the stable and "preview" options are way old and maybe not useful here.

@jonas0616
Copy link
Author

@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

@natevw
Copy link
Owner

natevw commented Sep 28, 2017

@jonas0616 Ah, excellent! So these should be an even handier debugging aid.

@miqueet
Copy link

miqueet commented Mar 6, 2018

Any word on alternative logic?

@jatpat
Copy link

jatpat commented Feb 14, 2019

it looks like working in latest Edge version 18.***

@natevw
Copy link
Owner

natevw commented Feb 14, 2019

Oh cool, maybe procrastination paid off then…?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants