Let's try removing the 'x' that's now smaller (but still above each tab) in the tabs tray. Pro: getting more of the title con: discoverability of swipe-to-dismiss Although, I think it's been a while since we've had swipe-to-dismiss so discoverability might not be so much of an issue anymore. Worth noting that we also have bug 1178794 for improving that interaction.

I wonder if long-pressing a tab is something people would do without the X. Currently we do not show a context menu for tabs.

Sounds like an A/B test. We should also make sure we have probes to monitor use of the 'x', use of swipe, and attempts to long press.

Actually the more I think about it, the more I don't think we should be removing the 'x'. The 'x' is the only visual prompt to hide a tab and I worry that some people won't know that there are other ways to do this (we don't tell them there are other ways and I feel like showing instructions means we have failed from a UX POV) and I fear that this move will be seen as removing a useful piece of UI for the sake of it - there's no massive win for this bug. I would, however, love to stick some telemetry in to see the number of people who use the 'x' compared to the number who swipe - also perhaps the number of people who have never swiped a tab close

(In reply to Martyn Haigh (:mhaigh) from comment #3) > I would, however, love to stick some telemetry in to see the number of > people who use the 'x' compared to the number who swipe - also perhaps the > number of people who have never swiped a tab close +1 to telemetry. We could land some probes to instrument what we have now, and then we could look into doing an A/B test as mfinkle suggested in comment 2.

(In reply to :Margaret Leibovic from comment #4) > (In reply to Martyn Haigh (:mhaigh) from comment #3) > > > I would, however, love to stick some telemetry in to see the number of > > people who use the 'x' compared to the number who swipe - also perhaps the > > number of people who have never swiped a tab close > > +1 to telemetry. We could land some probes to instrument what we have now, > and then we could look into doing an A/B test as mfinkle suggested in > comment 2. Yeah, I should have reversed the content of my comment: 1. Get enough data to figure out what's happening now. 2. If we need to change something, look into whether A/B testing is the right approach to figure out how to create the most successful outcome.

(In reply to Sebastian Kaspari (:sebastian) from comment #1) > I wonder if long-pressing a tab is something people would do without the X. > Currently we do not show a context menu for tabs. Are you picturing the long-press interaction on action bar icons in gmail? Cause I was thinking that... (In reply to Mark Finkle (:mfinkle) from comment #5) > (In reply to :Margaret Leibovic from comment #4) > > (In reply to Martyn Haigh (:mhaigh) from comment #3) > > > > > I would, however, love to stick some telemetry in to see the number of > > > people who use the 'x' compared to the number who swipe - also perhaps the > > > number of people who have never swiped a tab close > > > > +1 to telemetry. We could land some probes to instrument what we have now, > > and then we could look into doing an A/B test as mfinkle suggested in > > comment 2. > > Yeah, I should have reversed the content of my comment: > > 1. Get enough data to figure out what's happening now. > 2. If we need to change something, look into whether A/B testing is the > right approach to figure out how to create the most successful outcome. I agree, we need more data here to make an informed decision.

(In reply to Anthony Lam (:antlam) from comment #6) > (In reply to Sebastian Kaspari (:sebastian) from comment #1) > > I wonder if long-pressing a tab is something people would do without the X. > > Currently we do not show a context menu for tabs. > > Are you picturing the long-press interaction on action bar icons in gmail? > Cause I was thinking that... I was thinking about an ordinary context menu with options like "close". But thinking more about it a Contextual Action Mode would be interesting too: Long pressing a tab, then selecting multiple tabs if needed, and having actions in the action bar like close. This way you could perform actions on multiple tabs. And there might be more than just close.

(In reply to Sebastian Kaspari (:sebastian) from comment #7) > But thinking more about it a Contextual Action Mode would be interesting too: > Long pressing a tab, then selecting multiple tabs if needed, and having > actions in the action bar like close. This way you could perform actions on > multiple tabs. Definitely thought about this one too. Just like in your photos gallery! And I think the visual aspect of this grid makes it resemble a photo gallery a lot more too so the connection is more obvious. Definitely up for experimenting with this. > And there might be more than just close. Exactly! ;)

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.