[Tabs tray to Compose] too easy to swipe close a tab when flinging the tab list
Categories
(Fenix :: Tabs, defect)
Tracking
(Not tracked)
People
(Reporter: mark.paxman99, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:121.0) Gecko/20100101 Firefox/121.0
Steps to reproduce:
Enable Tabs tray to Compose
Open many tabs
Fling tabs list upwards eg using thumb so the gesture is mostly vertical but slightly diagonal
Actual results:
Very often the slightly diagonal upwards fling results in the swipe-to-close gesture and a tab closes. It's very very annoying.
This does NOT happen with the previous "non-Compose" tabs tray.
Expected results:
I think the Compose tab tray swipe-to-close logic only looks at the horizontal component of the fling velocity, so a fling gesture results in a swipe-to-close any time the horizontal velocity exceeds the threshold, even if the fling is mostly vertical. I think this is incorrect behavior.
I think the non-Compose tab tray looks at both components of fling velocity and prevents the swipe-to-close if the gesture is substantially vertical, even if the horizontal component of the swipe exceeds the swipe to close threshold. Much better.
Touch a tab and drag a few mm sideways as if to begin a swipe-to-close. Turn the gesture into a vertical fling:- swipe vigorously mostly vertically but with a slight horizontal component. The non-Compose tab snaps back and does not close, even if the fling is at ~45 degrees. The Compose tab usually closes, the fling has to be almost vertical to avoid it closing.
Comment 2•1 year ago
|
||
I am suffering from this issue as well, both grid and list view on beta and nightly. Tabs close insanely easily, I have to scroll tabs very very carefully to not close any, and a careless swipe to scroll is almost guaranteed to close a tab. Severely impacting user experience.
Comment 3•1 year ago
|
||
The severity field is not set for this bug.
:007, could you have a look please?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
Comment 4•1 year ago
•
|
||
Thanks for filing this bug! I'm closing this as a duplicate of Bug 1854335, so please follow that one for updates on this issue.
Description
•