Bugzilla

(In reply to Mark Hammond [:markh] [:mhammond] from comment #27)
> (In reply to Sarah Clements [:sclements] from comment #25)
> The initial report here was related to relevance, not privacy - ie, the reporter wanted the ability to *close* tabs once they are "done" with them. This then transformed into "we can't close them, how about we hide them?" as a vehicle for trying to ensure the 3 tabs Firefox View shows are relevant.
> 

You're right, and unfortunately I've caused some confusion here by duping the original privacy bug 1790853 which was the primary driver behind hiding the synced tabs. You can see the lengthy conversation about how to implement it in the doc Kelly linked to. Even though this bug has morphed in a less-than-ideal way, there's enough relevant conversation that it doesn't make sense to file a new bug just for the privacy angle. Let's keep this bug as-is and I'll file a bug to address the remote closing of tabs in Firefox View specifically.

> Re the privacy argument - I can't see any evidence there's an actual use-case there - if there was, it would have been raised over the years that synced tabs have existed - but that request/concern has never come up. The tab will still appear in autocomplete etc, and quite probably in the new tab page due to history syncing, so if privacy is a driver it will need more thought than just hiding the synced tab.
> 

In addition to the bug that Daniel filed, we've implemented the removal of tabs for Recently Closed tabs in Firefox View (see bug 1787945). Both of these bugs address privacy concerns specifically about Firefox View that were brought up in foxfooding. 

> The initial request (to close remote tabs) has come up before though - bug 1330816 - and the use-cases there are all about closing "obsolete" tabs, not about privacy. That bug is something we could scope out if product wanted it treated as a priority.

I guess I'm a bit confused about which PM's would be prioritizing it (Vesta since it's a sync wide thing, or the View PM's?).

UX is currently conducting user research of how people use Firefox View. AIUI, that information will be used to redesign aspects of the Tab Pickup section, which may very well address the original request for this bug. If that's the case, we can reach out about that.

(In reply to Mark Hammond [:markh] [:mhammond] from comment #27)
> (In reply to Sarah Clements [:sclements] from comment #25)
> The initial report here was related to relevance, not privacy - ie, the reporter wanted the ability to *close* tabs once they are "done" with them. This then transformed into "we can't close them, how about we hide them?" as a vehicle for trying to ensure the 3 tabs Firefox View shows are relevant.
> 

You're right, and unfortunately I've caused some confusion here by duping the original privacy bug 1790853 which was the primary driver behind hiding the synced tabs. You can see the lengthy conversation about how to implement it in the doc Kelly linked to, which to some degree explains the evolution of hiding to dismissing/blocking. Even though this bug has morphed in a less-than-ideal way, there's enough relevant conversation that it doesn't make sense to file a new bug just for the privacy angle. Let's keep this bug as-is and I'll file a bug to address the remote closing of tabs in Firefox View specifically.

> Re the privacy argument - I can't see any evidence there's an actual use-case there - if there was, it would have been raised over the years that synced tabs have existed - but that request/concern has never come up. The tab will still appear in autocomplete etc, and quite probably in the new tab page due to history syncing, so if privacy is a driver it will need more thought than just hiding the synced tab.
> 

In addition to the bug that Daniel filed, we've implemented the removal of tabs for Recently Closed tabs in Firefox View (see bug 1787945). Both of these bugs address privacy concerns specifically about Firefox View that were brought up in foxfooding. 

> The initial request (to close remote tabs) has come up before though - bug 1330816 - and the use-cases there are all about closing "obsolete" tabs, not about privacy. That bug is something we could scope out if product wanted it treated as a priority.

I guess I'm a bit confused about which PM's would be prioritizing it (Vesta since it's a sync wide thing, or the View PM's?).

UX is currently conducting user research of how people use Firefox View. AIUI, that information will be used to redesign aspects of the Tab Pickup section, which may very well address the original request for this bug. If that's the case, we can reach out about that.