Closed Bug 1178794 Opened 9 years ago Closed 4 years ago

Make "swipe-to-close" interaction feel more tangible

Categories

(Firefox for Android Graveyard :: General, defect, P5)

All
Android
defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: antlam, Unassigned)

References

Details

Filing this to keep track of improving this interaction. Right now, it works and is a "V1" of sorts. But it could definitely feel better and more tangible.
(In reply to Michael Comella (:mcomella) from bug 1180951 comment #0) > Maybe I'm just used to the phone behavior, but it requires a lot of momentum > to swipe away tabs on the tabs panel. Can the behavior be made more like the > phone implementation? > > e.g. if there's any momentum to the right when I swipe right, the tab should > be removed, rather than having to exceed some threshold. > > Anthony, any thoughts? (In reply to Anthony Lam (:antlam) from bug 1180951 comment #1) > I filed bug 1178794 to follow up on the feeling of this interaction. > > But, specifically on the "threshold" aspect, I think it's good to have that. > It's pretty standard behavior with these types of interactions and it really > helps avoid dismissal errors (which can be pretty bad, even if we have a > toast). I'm at the other end of the spectrum though where I try to swipe away a tab multiple times in a row and it just comes back every time. Not to say that we can't do better, but the phone tabs tray was never a problem for me - did you have issues with it?. Worth noting that we have undo for mistakes.
Blocks: tabs-tray-v3
No longer blocks: tabs-tray
It is going to be very hard to make a decision here since we have some people reporting 'too hard' and others reporting 'too easy' in the duplicates and comments. We could make a setting that adjusts the sensitivity of swiping away tabs. Somebody else would have to create the patch.
Thanks TenCapsule.com, The goal here is to make it feel more tanglible, and I think that's actually easier to validate compared to something being "too easy" or "too hard". The original animation and interaction design tried to copy more of what iOS Firefox did with the curved animation. I'd say that helps address issues of tangibility a bit better than the current implementation on Android. But I know this is a low priority item for the time being so we will have to wait and see the final designs before assessing more. Thanks for your input!
Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195 Needinfo :susheel if you think this bug should be re-triaged.
Priority: -- → P5
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.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.