Closed Bug 1274422 Opened 9 years ago Closed 9 years ago

Determine what sidebar activity should be persisted

Categories

(Hello (Loop) :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Mardak, Unassigned)

References

Details

(Whiteboard: [akita][uxtriage])

Bug 1274419 will implement the persisting, but it's unclear what should actually be persisted. In particular should prompts like asking to turn on webrtc bug 1274094 be persisted?
Whiteboard: [akita] → [akita][uxtriage]
(In reply to Ed Lee :Mardak from comment #0) > In particular should prompts like asking to turn on webrtc bug 1274094 be > persisted? I think it depends on what you mean by "persisted". I think if a owner has an offer out, and the guest reloads the page, the webrtc prompt should still be there. However, when owner leaves, the prompt should go away. Likewise, I believe the UX is that we don't have a history of prompts.
UX question: What items that show up in the sidebar should be persisted? The list should explicitly include or exclude things like WebRTC offers, connected states, join/leave events, and any other items that can show up in the sidebar.
Flags: needinfo?(sfranks)
Flags: needinfo?(b.pmm)
I've created a Google Doc for sidebar events here: https://docs.google.com/document/d/1L9a3U1QnRmIhgp0CJ-A-b-_63piky2QELe4AFr2EuyQ/edit Please help me fill in anything you think I have missed.
Flags: needinfo?(sfranks)
Flags: needinfo?(b.pmm)
Basically all items displayed in the sidebar should be persistent. We will decide which elements should be displayed or not but I prefer all being persistent and thus under our control rather than being something ethereal that we cannot control. Except the prompts that are displayed when a user joins the room, shares their screen with you, or turns on their camera/mic that appear and then either disappear upon user action or disappear by inactivity (timeout), the rest of events are going to be displayed always in the sidebar. Strings are not crucial at this point and it's something we need to start working on.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.