Cycle tabs in tab order still broken (with pinned tabs and tab stack)
-
Tab bar layout (Normal, Pinned, Stacked tabs):
P P SSS N SSS N N N when cycled in tab order leads to following order:
1 2 346 5 78 10 9 11 12 instead of
1 2 345 6 78 9 10 11 12in other words: before the last (third) tab in a stack is selected, the next tab outside the stack (left from it) is selected and only if cycling one more time, the last tab in a stack is selected.
All other (normal) tabs work properly.
It is 100% reproducible here in Win7 with latest stable version (1.14), tested with RMB+scroll wheel.
Can anybody confirm?
-
This has been bugging me lately too, so I tried your tab layout. Using RMB+wheel as well. Win10. "Cycle in tab order" selected. Result:
12 347 5 689 10 11 12So confirmed buggy, but a slightly different order than your result. Still in the wrong order though. Perhaps the order has something to do with the initial position of the tab when you stack it or something. It's definitely confusing.
-
Thank you for confirming!
Reported as VB-37188
-
I confirm that bug in 4.0.2312.33.
My case:
As you can see the tabs order in Tab Bar on the right side and in Tab List on the left side is different( -
I think think this problem exists only when there is pinned tabs. I resently deleted all my pinned tabs and problem is gone.
-
I see this without pinned tab.
"New Tab" with in a stack
and "New Top Level Tab" breaks the order without pinned tab. -
This is a very annoying bug.
Any timeline on when it's gonna be fixed? -
Wow, just noticed this post has been here since Feb 2018!!!
It's Aug 2021 now.
Guess I'm switching to Firefox. -
I'm pretty shocked to see this bug has been around since 2018 as well. I've noticed it a lot since I switched a few months back. I've loved almost everything with vivaldi except this bug. This bug is driving me crazy and causes a significant productivity impact and constantly takes my attention away from my work and back to this bug. How hard is cycling tabs in order, literally every other browser has been doing it since microsoft introduced tabs in IE7. This is pretty unacceptable.
-
This has been infuriating for me for a while too, particularly after the recent updates around stacking. It seems like it should be a simple thing to fix, and the negative impact on usability is huge.
-
Any update on this? Can you at least respect your users enough to confirm the bug?
-
@vafdibili I cannot reproduce it on Windows 10, using the latest Snapshot. What is your OS and Vivaldi version? Are you using Cycle in Tab Bar Order or Recently Used Order?
The developers rarely comment here; they are way too busy fixing them to follow up every topic in the forums.
You can ask in the official Bug Status thread about VB-37188, then someone with access to the bug-tracker can tell you its current status.
-
Vivaldi Version: 4.1.2369.21 (Stable channel) (64-bit)
Windows 10 Pro Version 21H1 Build 19043.1165The bug doesn't happen immediately that's why you can't reproduce it. Seems like when you open new tabs here and there the bug will show up.
-
@pesala Here's how to reproduce the issue:
- Open 4 tabs in the browser (let's call them A,B,C,D)
- Drag and drop B on A to stack them (it's now [A,B] , C, D )
- Go to tab A, and press Ctrl+T to open a new tab inside the stacked tab (it's now [A,B,E],C,D), .
- Now press Ctrl+Tab multiple times to see the bug.
-
I'm still getting an issue with keyboard tab switching (ctrl+tab and ctrl+shift+tab) in my browser (5.0.2497.28 (Stable channel) (x86_64) on MacOS 11.6)) with my main window, where it seems to randomly cycle through sub-tabs on various tabs, including tabs I haven't used for days when cycling in either order. For example, if I go ctrl+shift+tab from the current window, it cycles in the following order (T = tab, the first 3 of which are pinned; S = subtab)
T9S2 (of 3)
T9S1
T7S2 (of 16, instead of T8S3)
T8S3 (of 3)
T8S2
T8S1
T7S1 (instead of T7S16)
T3S7 (in a stack where the first subtab is pinned)
T3S6
T3S5
T6S3 (of 3)
T6S2
T6S1
T3S14
...However, when I opened a new window to try to recreate the issue using @Vafdibili 's steps I could not reproduce the error (I also played around with pinned tabs, quitting/restoring the session, and tiling tabs, but couldn't get the error to occur).
Obviously there is still a bug, since my main window is experiencing it, but I don't want to open a new bug without being able to give instructions to reproduce it. (And I really don't want to lose my session!)
Is anyone still able to reproduce the error according to @Vafdibili 's steps, and if not, has anyone found another combination of steps to be able to reproduce the error?
(spoiler for anyone reading this thread: they replied in the Bug Status thread that VB-37188 was fixed in 2018)
-
I wonder why Pinned Tabs have to journey of self-discovery to Left or Up Island.
How meanless that is?
"Stay with me" .
Knock on the door at midnight.
I cry out "Please don't leave me" . -