Tab sharing should cope with tab-tearing

RESOLVED INCOMPLETE

Status

P3
normal
Rank:
35
RESOLVED INCOMPLETE
4 years ago
2 years ago

People

(Reporter: standard8, Unassigned)

Tracking

unspecified
Points:
5
Dependency tree / graph
Bug Flags:
firefox-backlog +

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
When a user tears a tab, tab-sharing currently goes to the next tab in the current window.

I think it would make sense to follow the tab that is shared.
(Reporter)

Updated

4 years ago
Rank: 8

Comment 1

4 years ago
Hi RT, Hi Sevaan,

Can you verify the desired tab sharing behavior when a tab is "tore" off the current shared tab session?

I don't think the current behavior would be a ship stopper for 38 - so put as P2 that we could adjust.  But can change based on your input.
Rank: 8 → 26
Flags: needinfo?(sfranks)
Flags: needinfo?(rtestard)
Flags: firefox-backlog+
Priority: P1 → P2
If a user tears off the tab, sharing should follow it. This means that if the conversation window is in the bottom-right in Firefox, it should be brought over to the new torn-off tab.

When we apply clearer indication of sharing (e.g. the glow, badges) this should follow the torn-off tab too, which becomes the new shared window.
Flags: needinfo?(sfranks)

Comment 3

4 years ago
I agree with Sevaan there, seems to make more sense.
Flags: needinfo?(rtestard)
(In reply to Romain Testard [:RT] from comment #3)
> I agree with Sevaan there, seems to make more sense.

OK, this will require some engineering work. What's the priority here?
Points: --- → 5
Flags: needinfo?(rtestard)

Comment 5

4 years ago
I don't see this as a blocker for Fx38 or Fx39 since it's an edge case, does not create instability and there is a work-around. 
The work on context sharing is higher priority than this for Fx39.
Marking this as P3 since it seems to fit this definition better.
Flags: needinfo?(rtestard)
Priority: P2 → P3

Updated

4 years ago
Rank: 26 → 35
(Reporter)

Updated

3 years ago
Blocks: 1099241
(Reporter)

Updated

3 years ago
No longer blocks: 1115336
With the new experience and way we are treating tab sharing and windows, I think the current behavior is actually desired.  Sevaan?
Flags: needinfo?(sfranks)
I think for now, while the product is about sharing your tab, it would be best to follow the tab. In the future when it's about sharing multiple tabs, then it would make sense to remain with the current approach and stay with the window.

Why do you think the current behavior works best for the current case?
Flags: needinfo?(sfranks)
Right now implicitly we are binding Hello to one window.  I'm not even sure where or if we made a decision about that, maybe for now it's just fallen out of the implementation.  Because of this we implicitly have a scope of sharing that includes the window you are in and excludes other windows.  Though thinking through it, I could imagine how dragging the tab is a useful way to "fix" the session you are in – to isolate work, or even potentially the sharing session to a different window.

On the other side, laziness suggests we leave it as it is, as I don't believe that right now either behavior is easy to understand or make use of, so without a clear goal we should leave things as they are, and if we have a clear goal later we should articulate that in a new bug and with a clear purpose.
Sounds good to me. Another thing to test with users.
(Reporter)

Comment 10

2 years ago
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.