1947865 - ping.gg gives a Firefox unsupported warning

Status: NEW

(Web Compatibility :: Site Reports, defect, P2)

Description

[Jeff Muizelaar [:jrmuizel]]

Attachment: Screenshot 2025-02-12 at 3.35.45 PM.png

Comment 1

[Andreas Pehrson [:pehrsons]]

Tried the free trial and can confirm I see an Agora SDK in there. Updating with some SDPs shortly. Note Firefox works fine as "embedder", i.e. a remote viewer, which is meant for OBS or similar software.

Comment 2

[Andreas Pehrson [:pehrsons]]

Attachment: Local offer in Chrome, as sender

Comment 3

[Andreas Pehrson [:pehrsons]]

Attachment: Remote answer in Chrome, as sender

Comment 4

[Andreas Pehrson [:pehrsons]]

I see two video sources on chrome://webrtc-internals. One is 1280x720@30 and one is 640x360@15. Like on bug 1949441, bug 1286945 probably plays a role here.
Also note the two video m-sections have the non-standard fmtp lines x-google-min-bitrate=500 and x-google-min-bitrate=1024;x-google-start-bitrate=2500, respectively, probably as a way to increase quality. I see in outbound-rtp stats that targetBitrate is 500000 and 2500000, respectively, too.
I don't think there's a standardized way to achieve this. Jib, do you know if it's been discussed?

Comment 6

[Andreas Pehrson [:pehrsons]]

Spoofing the UA string seems to work fine. Bitrates are roughly what Chrome exhibited. Modulo the capture format issues with certain cameras I can't see any other deal breaking issues. Getting Agora to update their docs perhaps?

Comment 7

[Andreas Pehrson [:pehrsons]]

Let's get bug 1286945 fixed and revisit.

Comment 8

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

(In reply to Andreas Pehrson [:pehrsons] from comment #4)

Also note the two video m-sections have the non-standard fmtp lines x-google-min-bitrate=500 and x-google-min-bitrate=1024;x-google-start-bitrate=2500, respectively, probably as a way to increase quality. I see in outbound-rtp stats that targetBitrate is 500000 and 2500000, respectively, too.
I don't think there's a standardized way to achieve this. Jib, do you know if it's been discussed?

That's super-old SDP bandwidth negotiation, which apparently Google still supports but has discouraged in its own products for many years.

Per bug 1276368 and this fiddle (not mine), b=TIAS:2500000 might work.

But the most reliable standard way to control bandwith these days isn't through negotiation, but live client-side using setParameters and maxBitRate.

Comment 9

[Andreas Pehrson [:pehrsons]]

My question is about min- and start-bitrate, though.

Especially setting the start bitrate seems to be something sites do to get higher quality off the bat, not needing to wait for ramp-up from BWE.

Comment 10

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

I'm not aware of any efforts to standardize min- or start-bitrate, neither negotiated or as a setParameters parameter on the sender.

Higher quality off the bat sounds nice, but what information would the application have to know this won't backfire, that the browser doesn't have?

Comment 11

[Andreas Pehrson [:pehrsons]]

The site could know that the remote party has a good connection (an owned server) at a decent distance from the user (e.g. geo lookup). The user may also have set some preferences with the site because it knows its own connection is good.