Set "close tab activation" option to last in stack
-
@Pesala Pls read this post again carefully, https://forum.vivaldi.net/post/553215
Here is more easy to follow example:
You have a stacked tab with 5 tabs & some solo tabs on before/after said stacked tab, you are on the 2nd tab of the stacked tab. So if you close active tab & go to previous/next tab in orderly manner - you are suppose to landed on either 1st/3rd tab of said tab stack, right? But that doesn't always happen as intended, you could closed an active tab on the 2nd position of the stacked tab & end up in solo tab (or tab in another stacked tab) with a previous/next index order (but not in the previous/next tabbar position order)! LOL
Another example is when we select a group of tabs in batch by holding SHIFT key & click on a tab a few position away from the active tab, sometimes Vivaldi will also highlight a tab/stack outside of the selection range - but in reality it's not selected, it's just a visual glitch caused by "outdated/faulty" index after we reorder a tab out of a stacked tab & begin a new stack or create more solo tabs from said tab. This sort of complicated tab management usually will messed up the index real good. LOL
So yeah, this could be a bug, or simply a flawed design that manifest its undesirable side effect when we throw stacked tab function into the mix. -
Adding my vote for a solution to this as well. It is really disorienting for me to jump to a (seemingly random) tab stack when closing a tab in my current tab stack. I really only ever want to move to another stack manually.
-
+1 This bug is a hinderence for my productivity workflow.
-
This post is deleted! -
I have this issue in 2025. Why is there still not a fix?
-
@BaakerBhaai
Hi, this is a feature request not a bug and 35 users vote for it since 2021.
You can vote for it in the first post with the like button.Cheers, mib
-
@mib2berlin said in Set "close tab activation" option to last in stack:
@BaakerBhaai
Hi, this is a feature request not a bug and 35 users vote for it since 2021.
You can vote for it in the first post with the like button.Cheers, mib
Hey thanks for that, I just voted.
But it seems like this should be treated as a bug, not just a feature request.
Here is my argument: as per Vivaldi’s documentation tab stacks exist to “group tabs to avoid confusion”.
(Source: (https://help.vivaldi.com/desktop/tabs/tab-stacks/)).However, closing a tab in a stack activates external tabs, violating this core purpose.
Docs describe stacks as tools to isolate workflows (“Two-Level display”, “popup thumbnails” for in-stack navigation).
Features like “Open Tabs in Current Tab Stack” imply interactions should stay confined to the stack.
Current activation logic contradicts these principles, breaking organized navigation.According to Vivaldi’s bug reporting guidelines, a bug is defined as behavior that deviates from intended functionality. (Source: https://help.vivaldi.com/desktop/troubleshoot/reporting-a-bug-in-vivaldi/)
Therefore this is definitely a bug, a deviation from documented behavior and not a feature request.
Please consider reclassifying.
-
@BaakerBhaai
Then report it to the bug tracker, the Vivaldi team decide.
We are all users here, the developers usually don't read the forum.For information on how to report a bug, see this URL: https://vvld.in/how-to-report-bugs
Once that is done, please share the bug number (beginning with VB-).
Add your vivaldi.net username, please.
On the form, you can add your email address. Once submitted, you'll get a confirmation. You can reply to this with any logs or further info.Cheers, mib
-
Chiming in that this feature request would add a lot of predictability and elegance to the existing "Activate Left/Right in Tab Order" close tab behavior as well. Right now you have to make a lot of conscious choices when you close tabs to get the results you want. If you close the leftmost tab with the Activate Left you'll leave your tab stack. If open several links you need to go to the rightmost opened link instead of the closest tab or you'll have to navigate after each newly opened tab closure.
-
I came to ask this for Android, but I didn't know that it's the same on Windows. It's a counterintuitive default behavior.
