Closed
Bug 1171969
Opened 9 years ago
Closed 9 years ago
decide how to handle remoteVideoEnabled and mute states
Categories
(Hello (Loop) :: Client, defect)
Hello (Loop)
Client
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dmosedale, Assigned: standard8)
References
Details
(Keywords: regression, Whiteboard: [fixed by bug 1203529])
User Story
As a developer, I should be able to clearly understand how video being enabled is related to video being muted. Currently in the tree, we use (local|remote)Video(Enabled|Disabled) actions, and treat these as being interchangeable with whether or not that thing is muted. This isn't strictly true, as not having a camera may want different user experience than being muted, and there may be other issues as well, conceivably, though not necessarily, mixed up in bug 1171933.
No description provided.
Flags: firefox-backlog?
Reporter | ||
Comment 1•9 years ago
|
||
Note that the SDK video enabled event contains some information that may help us, or that we may want to expose: https://tokbox.com/developer/sdks/js/reference/VideoEnabledChangedEvent.html
Assignee | ||
Comment 2•9 years ago
|
||
This has been fixed by the work in bug 1203529.
Assignee: nobody → standard8
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Whiteboard: [fixed by bug 1203529]
Assignee | ||
Updated•9 years ago
|
Flags: firefox-backlog?
You need to log in
before you can comment on or make changes to this bug.
Description
•