Open Bug 1896424 Opened 1 year ago Updated 3 months ago

meet.google.com - Group Calling option is missing

Categories

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

Firefox 127
Desktop
All

Tracking

(Webcompat Priority:P2, Webcompat Score:6, firefox127 affected)

Webcompat Priority P2
Webcompat Score 6
Tracking Status
firefox127 --- affected

People

(Reporter: rbucata, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug, )

Details

(Keywords: webcompat:contact-in-progress, webcompat:site-report, Whiteboard: [webcompat:sightline])

User Story

platform:windows,mac,linux
impact:feature-broken
configuration:general
affects:all
diagnosis-team:video-conferencing
branch:release

Attachments

(2 files)

Environment:
Operating system: Windows 10
Firefox version: Firefox 125.0.3, Nightly 127.0a1

Preconditions:
Account previously created

Steps to reproduce:

  1. Navigate to: https://meet.google.com/calling/ and perform account login
  2. Access: https://meet.google.com/calling/ again
  3. Dismiss the error message (unsupported)
  4. Observe the options below the page title "Start a video call"

Expected Behavior:
The "Create a group link" option is present

Actual Behavior:
The "Create a group link" option is missing

Notes:

  • Reproduces regardless of the status of ETP
  • Reproduces in Firefox Nightly, Firefox Release
  • Does not reproduce in Chrome

Created from https://github.com/webcompat/web-bugs/issues/136950

Attached video 20240513_175357.mp4
OS: Unspecified → All
Hardware: Unspecified → Desktop
Version: unspecified → Firefox 127
Severity: -- → S3
User Story: (updated)
Priority: -- → P2
Priority: P2 → P1

Note: the error message that the reporter says to dismiss is "Use the latest version of Google Chrome to enable group calls. More browsers will be supported in the future."
FYI @jimm

Flags: needinfo?(jmathies)
Blocks: meet
Flags: needinfo?(jmathies)
Attached image Prompt

As the prompt shows this is the old Google Duo, merged into Meet. It doesn't work in Safari either.

I was unable to get in using a custom UA string — not surprising since regular Meet falls over then as well (I suspect reliance on UA sniffing rather than feature detection) — so I can't tell what features are missing here, if any.

My guess: Google Duo touted E2EE quite a bit in its day, so that's probably why.

The good news is both Firefox and Safari support E2EE now, but it would require Meet to use workers and program against the standard API. See https://blog.mozilla.org/webrtc/end-to-end-encrypt-webrtc-in-all-browsers/

User Story: (updated)
Group: mozilla-employee-confidential
Depends on: 1913599

clearing internal status for this bug.

Group: mozilla-employee-confidential
Depends on: 1915169
No longer depends on: 1913599
See Also: → 1913599
Depends on: 1913599
No longer depends on: 1915169
See Also: 19135991915169
Whiteboard: [webcompat:sightline]
Webcompat Priority: --- → P2
Webcompat Score: --- → 6

Any updates?

Flags: needinfo?(jmathies)
Flags: needinfo?(jmathies)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: