This happens when there is not enough horizontal space for the entire tab bar to fit in. After Krusader has started and reloaded the last session, the tab bar will jump every time a tab far enough to the right is selected with a mouse click for the first time. After the jump, the tab is positioned as far to the right as possible.
Thanks for your interest. Can you attach screenshots to this bug report?
Created attachment 112911 [details] Tabs jump on first selection of a tab (In reply to Toni Asensi Esteve from comment #1) > Can you attach screenshots to this bug report? The first image shows the tab bar of the left panel after Krusader has been startet. There are 13 open tabs and they do not fit all into the horizontal space. The second image shows the situation after selecting tab number 11 with a mouse click: all tabs have made a jump to the right and tab 11 is now as far to right as it can be while still being visible. This annoying behavior happens only when tab 11 has not been selected before in the current Krusader session. Repeating the test with selecting tab 11 a second time in the same session would not change the position of the tabs. Selecting another previously unselected tab causes a jump if the first tab is not fully visible.
Confirmed on v2.7.0. This may be not a Krusader issue but some dependency issue. Need investigation what's causing this. Note: you don't have to reload the app. If you browse files in a tab, it also goes far right as soon as you change the dir. Just have enough tabs open for enabled scrolling of tabs to repro this.
Did some bugfinding: Looks like the QTabBar::setTabText() and QTabBar::setTabIcon calls in PanelTabBar are causing this. So yes, this could be a Qt issue.
There is the same problem with the KrViewer's tab bar, only worse. When I try to scroll to the right, the tabs will jump back immediately, making it impossible to access the tabs that are out of view.
Still in 2.7.2. Very annoying issue.
I think this has been fixed at least in the current master version. Can somebody confirm?
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.