Bugzilla

(In reply to Mark Hammond [:markh] [:mhammond] from comment #27)
> The initial report here was related to relevance, not privacy [...]  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.

Counterpoint: it has come up. My dupe bug 1790853 focused on the privacy argument.  It was duped here, but perhaps we should un-dupe it if we want to consider it separate?

> 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.

That might be an issue, yeah.

Notably, all of those other contexts (autocomplete, new-tab-page, and also the Show All History window) each off their own UX for deleting the unwanted site from your history.  I suppose our "Synced Tabs" menu UI doesn't offer that, but it's also not as obvious/discoverable as Firefox View intends to be.

Anyway: from my perspective, a potentially-ephemeral "Remove" option is fine for the scenarios in my dupe bug.  If someone really wants to purge an embarassing site from their history, they will likely want to dig in a bit deeper and we don't want to build that UX into Firefox View.  I was mostly focusing on having a quick intervention available for someone who's e.g. about to do a screencast or have shoulder-surfers, and realizes that a prominent piece of Firefox UI is surfacing a piece of history that they consider to be sensitive for whatever reason.

(In reply to Mark Hammond [:markh] [:mhammond] from comment #27)
> The initial report here was related to relevance, not privacy [...]  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.

Counterpoint: it has come up. My dupe bug 1790853 focused on the privacy argument.  It was duped here, but perhaps we should un-dupe it if we want to consider it separate?

> 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.

That might be an issue, yeah.

Notably, all of those other contexts (autocomplete, new-tab-page, and also the Show All History window) each off their own UX for deleting the unwanted site from your history.  I suppose our "Synced Tabs" menu UI doesn't offer that, but it's also not as obvious/discoverable as Firefox View intends to be.

Anyway: from my perspective, a potentially-ephemeral "Remove" option is fine for the scenarios in my dupe bug.  If someone really wants to purge an embarrassing site from their history, they will likely want to dig in a bit deeper and we don't want to build that UX into Firefox View.  I was mostly focusing on having a quick intervention available for someone who's e.g. about to do a screencast or have shoulder-surfers, and realizes that a prominent piece of Firefox UI is surfacing a piece of history that they consider to be sensitive for whatever reason.

(In reply to Mark Hammond [:markh] [:mhammond] from comment #27)
> The initial report here was related to relevance, not privacy [...]  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.

Counterpoint: it has come up. My dupe bug 1790853 focused on the privacy argument.  It was duped here, but perhaps we should un-dupe it if we want to consider it separate?

> 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.

That might be an issue, yeah.

Notably, all of those other contexts (autocomplete, new-tab-page, and also the Show All History window) each offer their own UX for deleting the unwanted site from your history.  I suppose our "Synced Tabs" menu UI doesn't offer that, but that menu is also not as obvious/discoverable as Firefox View intends to be.

Anyway: from my perspective, a potentially-ephemeral "Remove" option is fine for the scenarios in my dupe bug.  If someone really wants to purge an embarrassing site from their history, they will likely want to dig in a bit deeper and we don't want to build that UX into Firefox View.  I was mostly focusing on having a quick intervention available for someone who's e.g. about to do a screencast or have shoulder-surfers, and realizes that a prominent piece of Firefox UI is surfacing a piece of history that they consider to be sensitive for whatever reason.