Open
Bug 1431543
(meet)
Opened 7 years ago
Updated 1 year ago
[meta] issues affecting Hangouts/Meet
Categories
(Core :: WebRTC, task, P2)
Core
WebRTC
Tracking
()
NEW
People
(Reporter: drno, Unassigned)
References
(Depends on 5 open bugs)
Details
(Keywords: meta)
Meta bug for tracking all issues related to Google Hangouts and Meet.
Reporter | ||
Updated•7 years ago
|
Rank: 15
Reporter | ||
Updated•7 years ago
|
Comment 1•6 years ago
|
||
Hey Nils I have filed three bugs today that should all be tagged to this one: 1465253, 1465255, and 1465257 Let me know if you'd like to discuss them. The other largest issue we have since last week's launch is a proportionally high level of failure to establish ice connectivity, compared to chrome users. We're having trouble debugging that one since we don't have any internal repros or moz_log files, and any particular case could indicate legitimate firewall issues. Perhaps firefox doesn't have some functionality to navigate particularly onerous proxies.
Updated•6 years ago
|
Reporter | ||
Updated•6 years ago
|
Alias: hangouts
Updated•5 years ago
|
status-firefox72:
--- → affected
Updated•4 years ago
|
Depends on: CVE-2020-12416
![]() |
||
Updated•3 years ago
|
Webcompat Priority: --- → ?
![]() |
||
Updated•3 years ago
|
Webcompat Priority: ? → ---
Updated•3 years ago
|
Comment 3•3 years ago
|
||
I moved the webcompat link in See Also to bug 1468986.
Severity: normal → --
Updated•3 years ago
|
Type: enhancement → task
Comment hidden (off-topic) |
Updated•2 years ago
|
Flags: needinfo?(mfroman)
Comment 5•2 years ago
|
||
Sorry, there was a problem with the detection of inactive users. I'm reverting the change.
Assignee: nobody → drno
Updated•2 years ago
|
![]() |
||
Updated•1 year ago
|
Alias: hangouts → meet
Assignee: drno → nobody
You need to log in
before you can comment on or make changes to this bug.
Description
•