Closed Bug 1644556 Opened 4 years ago Closed 4 years ago

webconf.numerique.gouv.fr tells that my browser deteriorates the conference quality

Categories

(Core :: WebRTC, defect)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1210175
Tracking Status
firefox77 --- wontfix
firefox78 --- wontfix
firefox79 --- wontfix

People

(Reporter: jerome.bouat, Unassigned)

References

Details

(Keywords: parity-chrome, parity-edge)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

Open the bellow link :
https://webconf.numerique.gouv.fr/

Actual results:

A windows tells that my web browser highly deteriorates the quality of the web conference for all participants.

Expected results:

Firefox should work properly on this web site which relies on the open source Jitsi web conference. Moreover, this warning is a bad advertisement for Firefox.

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:77.0) Gecko/20100101 Firefox/77.0

Hi,

I have managed to reproduce this issue on release version 77.0.1, Beta 78.0b7 and latest Nightly 79.0a1 (2020-06-14) using Windows 10 as well. I will move this over to a component, if this is not the correct component please feel free to change it to an appropriate one.

Thanks for the report.

Status: UNCONFIRMED → NEW
Component: Untriaged → WebRTC
Ever confirmed: true
OS: Unspecified → All
Product: Firefox → Core
Hardware: Unspecified → All
Version: 68 Branch → Trunk

This is almost certainly due to bug 1210175.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE

Are you sure it is related to H264 ?
It seems that Jitsi sets VP8 as default codec.

(In reply to Jérôme from comment #3)

Are you sure it is related to H264 ?
It seems that Jitsi sets VP8 as default codec.

The warning is not coming from Jitsi, it is coming from a website that happens to use Jitsi, and the lack of H264 simulcast support has made Jitsi conferences really problematic in the past. They may have implemented VP8 simulcast in the meantime.

You need to log in before you can comment on or make changes to this bug.