Skip to content

Conversation

@fancycode
Copy link
Member

Older versions of Chrome (< 124) required the flag to be passed when creating PeerConnections so "createEncodedStreams" can be used later.

See https://issues.chromium.org/issues/40943169 and https://chromiumdash.appspot.com/commit/ae3454745ca8f623435d658eba7d4bc2dc8aed17

With that also refactored the browser detection of features for E2EE.

The issue happened on one of my machines still on Chrome 122 (was developing on Chrome 132 which doesn't need the flag).

Older versions of Chrome (< 124) required the flag to be passed when
creating PeerConnections so "createEncodedStreams" can be used later.

See https://issues.chromium.org/issues/40943169 and
https://chromiumdash.appspot.com/commit/ae3454745ca8f623435d658eba7d4bc2dc8aed17

With that also refactored the browser detection of features for E2EE.

Signed-off-by: Joachim Bauch <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review bug feature: call 📹 Voice and video calls feature: frontend 🖌️ "Web UI" client feature: WebRTC 🚡 WebRTC connection between browsers and/or mobile clients

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants