[WIP] Add WebRTC features to Linux #277
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
FYI for anyone coming across this, if I remember correctly from testing, the core problem lies in the fact that |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is a starting point to enable media/WebRTC features to Linux currently it allows to get to this point :
But the issue lies with the
navigator.getUserMedia()this API is deprecated and not available in webkitGTK and nownavigator.mediaDevices.getUserMedia()must be used, and using some polyfill or dirty JS injection doesn't solve the problem.I'm putting this as a draft PR if one day either Discord or webkit changes something so it can be merged.
In the mean time if someone has an idea you are welcome to modify the code.