Jitsi-meet: Support for Edge as it is Chromium-based now

[rickgoud]

Tt appears that Edge is not supported, although, since January, it is a Chromium based browser. Did someone already test whether specific changes are needed?

Supporting that would be awesome as a lot of public healthcare and governmental organizations still use Microsoft based browsers.

[samkho]

Edge Chromium works great for me. However, I had to go download it -- my old non-Chromium Edge did not update itself to the Chromium-based Edge.

[rickgoud]

Your absolutely right! But maybe then good idea to name this explicitely in the 'Not supported browsers'-list as one of the supported browsers?

[Echolon]

rel.
100% support for Firefox (and other non-Chrome browsers) #4758

[saghul]

@rickgoud Do you mean the desktop version (which IS supported) or the Android one?

[rickgoud]

Hi @saghul ! On desktop
The issue here was that
1) The 'normal' Edge (not manually updated to the Chrome version appreantly you need to do that manually!), did not work
2) Edge was not named on the Unsupported Browsers list
3) Edge with Chromium works

Do ideally:

• The Unsupported Browser page should include that Edge based on Chromium works
• Even better; also state that the user has an old version of Edge that is not supported and that the update should be mannually installed from here: https://www.microsoft.com/en-us/edge

Does this help?

[JimBobSquarePants]

Edge with Chromium works

Edge 83.0.474.0 was not working as of yesterday. No sound, with all other users marked as muted.

[pdarcos]

Now I'm confused. Does Edge on desktop work or not with jitsi-meet?

[saghul]

@JimBobSquarePants what do you see on the JS console?

[jmutchek]

I saw the same behavior as @JimBobSquarePants today, but only on Edge Dev. I'm using https://meet.jit.si/ from Edge Version 83.0.478.5 (Official build) dev (64-bit). I can join the same meeting from the released version of Edge Chromium (Version 81.0.416.53 (Official build) (64-bit)) and audio works fine.

There is a reference to audio issues in Edge Dev Known Issues (not sure if it is related).

This is the error I see in the JS console on Edge Dev:

Uncaught DOMException: Failed to execute 'createEncodedAudioStreams' on 'RTCRtpReceiver': Encoded audio streams not requested at PC initialization at c.handleReceiver (https://web-cdn.jitsi.net/meetjitsi_4004.656/libs/lib-jitsi-meet.min.js?v=3962.622:17:26055) at se.onRemoteTrackAdded (https://web-cdn.jitsi.net/meetjitsi_4004.656/libs/lib-jitsi-meet.min.js?v=3962.622:10:172263) at a.emit (https://web-cdn.jitsi.net/meetjitsi_4004.656/libs/lib-jitsi-meet.min.js?v=3962.622:1:126857) at se._addRemoteTracks (https://web-cdn.jitsi.net/meetjitsi_4004.656/libs/lib-jitsi-meet.min.js?v=3962.622:10:183868) at se._addRemoteP2PTracks (https://web-cdn.jitsi.net/meetjitsi_4004.656/libs/lib-jitsi-meet.min.js?v=3962.622:10:183663) at se._onIceConnectionEstablished (https://web-cdn.jitsi.net/meetjitsi_4004.656/libs/lib-jitsi-meet.min.js?v=3962.622:10:184945) at a.emit (https://web-cdn.jitsi.net/meetjitsi_4004.656/libs/lib-jitsi-meet.min.js?v=3962.622:1:126857) at C.peerconnection.oniceconnectionstatechange (https://web-cdn.jitsi.net/meetjitsi_4004.656/libs/lib-jitsi-meet.min.js?v=3962.622:1:192329) at RTCPeerConnection.C.peerconnection.oniceconnectionstatechange (https://web-cdn.jitsi.net/meetjitsi_4004.656/libs/lib-jitsi-meet.min.js?v=3962.622:10:114722)

[saghul]

Oops, that's ddue to the E2EE code. Will fix, thanks for the report!

[saghul]

Fixed in https://github.com/jitsi/lib-jitsi-meet/pull/1094

Note that this not related to Edge, it would happen also in Chrome Canary with the experimental Web Platform flag set.

[JimBobSquarePants]

@jmutchek Beat me to a response, thanks!

Great work getting a fix in so quickly. Really impressed with everything I've seen so far! 👍

[edvanleeuwen]

Great job, saw that it already has been approved and merged with the master branch. How soon will this be available after this?