Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

[Bug]: Scroll position in tab list does not show active tab #20932

Closed
WesleyAC opened this issue Aug 19, 2021 · 4 comments
Closed

[Bug]: Scroll position in tab list does not show active tab #20932

WesleyAC opened this issue Aug 19, 2021 · 4 comments
Labels
🐞 bug Crashes, Something isn't working, .. needs:triage Issue needs triage

Comments

@WesleyAC
Copy link

WesleyAC commented Aug 19, 2021

Steps to reproduce

With many active tabs open, click on the tab switcher.

Expected behaviour

The active tab should be visible in the viewport.

Actual behaviour

Often, the active tab will not be scrolled into the viewport — instead, the view will either be scrolled to the complete bottom, or the complete top.

Device name

Google Pixel 3a

Android version

Android 11

Firefox release type

Firefox Nightly

Firefox version

93.0a1

Device logs

No response

Additional information

I have my tabs settings as:

  • Tab view: List
  • Close tabs: Manually

I'm not sure if this is relevant, though.

┆Issue is synchronized with this Jira Task

@WesleyAC WesleyAC added needs:triage Issue needs triage 🐞 bug Crashes, Something isn't working, .. labels Aug 19, 2021
@marcel263
Copy link

also #19943

@jonalmeida
Copy link
Contributor

Do you have any inactive tabs in your tray list? This might be a duplicate of #20637.

I'm not sure if this is relevant, though.

It is helpful, thanks. 🙂

@argymeg
Copy link

argymeg commented Oct 30, 2021

Can confirm this is happening for me again as well (it had stopped for a while after the closure of #20637). I have no inactive tabs. The workaround mentioned in the closure of #22116 also made no difference.

@jonalmeida
Copy link
Contributor

Can confirm this is happening for me again as well (it had stopped for a while after the closure of #20637). I have no inactive tabs. The workaround mentioned in the closure of #22116 also made no difference.

Could you file a new bug with STR how you reproduced it? We fixed this already in #21177 so if there is a regression, let's file it as such.

Closing this issue, since we forgot to tag it in #21177 and have it auto-closed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🐞 bug Crashes, Something isn't working, .. needs:triage Issue needs triage
Projects
None yet
Development

No branches or pull requests

4 participants