Skip to content

fix: Enable "encodedInsertableStreams" on browsers supporting it.#15197

Open
fancycode wants to merge 1 commit into
mainfrom
fix-enable-encoded-insertable-streams
Open

fix: Enable "encodedInsertableStreams" on browsers supporting it.#15197
fancycode wants to merge 1 commit into
mainfrom
fix-enable-encoded-insertable-streams

Conversation

@fancycode

Copy link
Copy Markdown
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 <bauch@struktur.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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.

3 participants