ToC prevents itself from being unpinned, closed, or moved into its own window

RESOLVED INCOMPLETE

Status

Hello (Loop)
Client
P2
normal
Rank:
21
RESOLVED INCOMPLETE
2 years ago
2 years ago

People

(Reporter: dmose, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [akita] [needs-prototype])

User Story

As a room owner, I should be unable to inadvertently lose track of the ToC tab by unpinning or closing it.  

Acceptance criteria:

* "Pin Tab", "Move to new Window", "move to new non-e10s window", "Close Tab" are hidden in the ToC tab context menu
* "Close other tabs", "Close tab to the right" in the tab context menu has no effect on the ToC
* Middle-click on ToC tab does not close it
* Dragging the ToC tab out of the dedicated window has no effect

Tech notes:
* presumably, we'll want to do this at ToC initialization time, probably as a LoopAPI request to the chrome code
(Reporter)

Description

2 years ago
This needs a prototype in order to estimate it.  We should bias towards the simple, and consider other UX if that's not easily available.
(Reporter)

Comment 1

2 years ago
@sevaan, @pau: I'm assuming we don't want to allow the ToC tab to be moved into its own window.  Is that correct?
User Story: (updated)
Flags: needinfo?(sfranks)
Flags: needinfo?(b.pmm)
(Reporter)

Updated

2 years ago
User Story: (updated)
(In reply to Dan Mosedale (:dmose) from comment #1)
> @sevaan, @pau: I'm assuming we don't want to allow the ToC tab to be moved
> into its own window.  Is that correct?

Yes that is correct, thanks.
Flags: needinfo?(sfranks)
Flags: needinfo?(b.pmm)
Rank: 21
Priority: P1 → P2
Support for Hello/Loop has been discontinued.

https://support.mozilla.org/kb/hello-status

Hence closing the old bugs. Thank you for your support.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.