Tapping tabs overview does not show current tab V2
Categories
(Fenix :: Tabs, defect)
Tracking
(Not tracked)
People
(Reporter: cpeterson, Unassigned)
Details
From github: https://github.com/mozilla-mobile/fenix/issues/28567.
Steps to reproduce
Repeat a couple of times:
- Click tab overview
- Select a tab
Note that I have many tabs opened (100).
Expected behaviour
The preselected tab is the current one and it is visible.
Actual behaviour
About every five times the overview scrolls all the way up to the very first tab of the list. I have to scroll down a lot every time.
Device name
Oneplus 7
Android version
Android 11
Firefox release type
Firefox
Firefox version
Fennec 108.1.1
Device logs
No response
Additional information
This has been going on for a year or so. I am annoyed. I might have to use another browser so I don't jump out of the window.
┆Issue is synchronized with this Jira Task
Change performed by the Move to Bugzilla add-on.
Comment 1•2 years ago
|
||
I looked into it some more and would like to add some detail.
By now I can reproduce the issue on a freshly installed Firefox Android 109.1.1 like this:
- open a couple of tabs (internet connection not necessary)
- wait for two weeks (tabs will be moved to "inactive tabs")
- with the "inactive tabs" expanding button at the top of the tab overview open about 10 tabs so that you can scroll
- repeat: open tabs overview and select the tab at the bottom
- after 1-25 times the tab overview will scroll to the top
There seems to be a (timing?) issue with the inactive tabs button hiding before the tabs show up. With the bug the tabs show faster, so the delay the animation is causing is anoying by itself even if it would work properly. There is a related issue about this: https://github.com/mozilla-mobile/fenix/issues/13293 If I could disable animations maybe it would work properly, but how?
Basically this issue makes archived tabs unusable for me.
This is a typical feature/bug that makes me wonder whether a competing corporate double agent sabotaged Fenix.
Comment 2•2 years ago
|
||
Closing as Bug 1824581 already captures this bug and has a larger discussion on the topic.
Description
•