Open Bug 1945323 Opened 5 months ago Updated 25 days ago

guest.lifesize.com - Firefox is unsupported browser

Categories

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

Firefox 128

Tracking

(Webcompat Priority:P2, Webcompat Score:5)

UNCONFIRMED
Webcompat Priority P2
Webcompat Score 5

People

(Reporter: jerome.bouat, Unassigned)

References

(Depends on 1 open bug, )

Details

(6 keywords)

User Story

platform:windows,mac,linux,android
impact:blocked
configuration:general
affects:all
branch:release
diagnosis-team:video-conferencing
user-impact-score:200

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

Steps to reproduce:

Open the web site :
https://guest.lifesize.com/

Actual results:

I get an error message which tells :
"It looks like you are using Firefox…
Unfortunately, Firefox does not support our web experience.
Let’s install the Lifesize app instead so you can get to your meeting fast."

Expected results:

Firefox should work with this web site. No application should be installed on the host in order to use this service (not all platforms available and no admin authorization). No warnings should be displayed for newer versions of Firefox.

OS: Unspecified → All
Hardware: Unspecified → All

With a spoofed UA string (but for the webapp. subdomain), I at least see the login screen. It's probably worth checking if we can test this app somehow.

Severity: -- → S2
User Story: (updated)
Webcompat Priority: --- → P2
Webcompat Score: --- → 6
Priority: -- → P2

Seems like Lifesize filed for bankruptcy and was then (to some degree) acquired by Enghouse, which also owns Vidyo. Vidyo has some developer info on https://www.enghousevideo.com/develop-video-app-platform, including a link to an online demo. I can get quite far with the online demo, but creating and joining a room eventually fails. Joining one already created is not possible, as it forces you to download their app.

Chrome works as expected on both creating and joining rooms, and transferring media to a remote Chrome peer.

Spoofing as Chrome doesn't seem to help.

Not sure how related Lifesize and Vidyo really are these days, but they are at least officially linked.

See Also: → 1899050
Keywords: losing-users
Keywords: reproducible
Webcompat Score: 6 → 5

I can make the vidyo connect demo in comment 2 work by allowing mid munging (which is forbidden by spec). AFAICT they munge our mids ("0", "1", "2", "3") to "L0", "L1", "L2", "L3", respectively. Doesn't seem to critical but who knows.

Doesn't seem like one can create an account with lifesize. guest.lifesize.com is the entry they have for inviting users without accounts into meetings, but you cannot get to the call setup without a valid "extension". I can enter an invalid one and get it to ring for a second, but no peer connection is even created. From what I can tell, the hair-check (local audio/video) works fine. I do see ServiceWorkerContainer.register rejecting with a security error. For the curious the web console also says

Call-signaling configuration settings set: 
{
  audioInPresentation: true,
  directMedia: true,
  enableLogging: false,
  endpoint: { info: "Guest Web App (1.1.12-20425) Chrome/127.0.0.0 macos/10.15" },
  forceTcpTunneling: false,
  locale: "en",
  receiveStreams: 9,
  sdpOptions: {
    bwPercentage: 0.5,
    enable1080Rx: false,
    maxBandwidth: 2048,
    noModifications: false,
​​    preferH264: true,
​​    preferredProfile: "42e01f",
    splitBandwidth: true,
  },
  supportRelayMode: false,
  useAddTrack: false,
}

I guess the {sdpOptions: {noModifications: false}} may mean (munging) trouble.

All this with UA string spoofed as Chrome 127 on macOS.

Removing needs-diagnosis until we can get a way to reproduce.

No longer blocks: webrtc-triage
You need to log in before you can comment on or make changes to this bug.