Treestyletab: Changing tabs causes TST's scroll position to jump

Created on 9 Feb 2018  路  7Comments  路  Source: piroor/treestyletab

Short description

Each tab focus change (whether by clicking a tab or closing one) causes the scroll position of TST's tab tree to jump up such that the newly-focused tab is _always_ out of view.

Example:
untitled project

Steps to reproduce

_Not_ reproduceable. Opening a large number of tabs in a new profile and clicking around yields expected (good) behaviour. I'm filing this entirely as a question:

What in my profile could possibly cause this kind of bizarre scrolling behaviour? The rest of the browser is operating as expected.

(Thank you very much for all of your work on this project. 馃槃 )

Environment

  • Platform (OS): Windows 10
  • Version of Firefox: 58.0.2
  • Version (or revision) of Tree Style Tab: 2.4.12
partially fixed

Most helpful comment

Same problem here.

I think I found how to resolve it: collapse all your group of tabs, then close Firefox and reopen it.

Tree Style Tab 2.4.18
Firefox 59.0.2 (Windows 10)

All 7 comments

I am experiencing something like this also. I have two windows both with dozens of tabs. One of them behaves normally. The other behaves like this: whenever you click on a tab it scrolls all the way up to the first tab. This is very annoying when you have lots of tabs.
MacOS, Tree Style Tab 2.4.17, FF 58.0.2

Same problem here.

I think I found how to resolve it: collapse all your group of tabs, then close Firefox and reopen it.

Tree Style Tab 2.4.18
Firefox 59.0.2 (Windows 10)

This problem will happen when collapsed/expanded state of tabs are mis-detected. TST calculates the destination scroll position based on tabs detected as "expanded" (aka "visible"). However, by some reasons, collapsed state of tabs can be mismatched between the sidebar contents and the background (invisible) page.

Updated: I've realized that this problem is caused when there are many numbers of preceding tabs which are visible but have the collapsing class. I cannot find out what causes this status yet...

Thanks very much @Aymkdn for sharing your workaround. It seems to work! I am now able to use TST without frustration :-) I only had to close all the root nodes and restart to fix it.

Anyway, the commit ae03533 should reduce frequency of happening this problem.

@cemerick are you still having issues? If not, can you close this?

No, this seems settled, closing.

Was this page helpful?
0 / 5 - 0 ratings