Expose WebRTC API to extensions

[t-mullen]

It would be great if VSCode could expose the WebRTC API from it's render process to extensions.

Currently there's no way to use WebRTC in extensions barring including a wrtc binary for every operating system (which is obviously not an option) or spawning a whole new electron process.

Ideally, extensions could have full access to the render process like other editors allow, but I know this has been brought up several times before.

This would unlock an enormous number of awesome P2P applications.

[t-mullen]

Spawning an electron process doesn't work due to how the packager works. So there's really no way to do this without including multiple large binaries or having the user manually install electron.

Some applications include the DAT project, FTP via WebTorrent, and countless others.

I'd really like VSCode to join the other web-based editors in supporting this technology.

[jrieken]

It's part of our isolation designed that don't expose 'the' renderer process which owns the editor/blinking cursor. What you are suggesting more like using a renderer process for the extension host process

[vscodebot]

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that have been on the backlog for a long time but have not gained traction: We look at the number of votes the issue has received and the number of duplicate issues filed. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!