Set "close tab activation" option to last in stack
-
Come on vivaldi team
-
Yes, please let us stay in a tab stack. By using all features yourselve or at least one of the dev team you'll notice these kinds of things immediately and want to fix them.
-
I'd love to see this fix: it's the biggest frustration I have with Vivaldi. I often have different "projects" on the go in different tab stacks and closing the last tab in the stack shouldn't take me to a different tab stack.
-
Ppafflick moved this topic from Automotive Feature Requests on
-
Can we got an answer from vivaldi team if this problem is at least acknowledged?
-
@RK900 There are over 5,000 feature requests. The Vivaldi Team cannot possibly add them all. You will see the thread tagged as In Progress if the status changes.
With only 11 votes, this is probably very low on the list of priorities.
I suggest setting tab activation to Activate Right in Tab Order
-
@Pesala said in Set "close tab activation" option to last in stack:
I suggest setting tab activation to Activate Right in Tab Order
That won't solved the problem at all, because the next/right orderly tab could be outside of current active stack - so when you close active tab within/outise a stack, it suppose to focus on the next/right in order tab, right? But in reality it doesn't! Because Vivaldi "forgot" to reindex all tab's order after we create/modified stacked tab. Please refer to my previous post explanation (https://forum.vivaldi.net/post/553215). Basically either this is cause by an oversight flawed design, or a bug.
There are over 5,000 feature requests. The Vivaldi Team cannot possibly add them all. You will see the thread tagged as In Progress if the status changes.
With only 11 votes, this is probably very low on the list of priorities.I don't want to sounds like being rude to you, but please stop spamming the same "There are over 5,000 feature requests. The Vivaldi Team cannot possibly add them all." excuse already.
This is not a bug/problem that appear long after tab stacking function were introduced, it was introduced TOGETHER with stacking function. Basically, it's broken since day 1 when stacking is introduced. It just nobody noticed it in the very early days (& somehow it get pass QA testers?), but then v-team decided to move on to another new feature instead of fixing this problem/bug when people begin to notice & complain about it.
@RK900 File a bug report on this one, IMHO this should have being consider as a bug since the beginning.
-
-
@RK900
Hi, the "Report to the forum" is meant as you post an issue to the forum, if other user can reproduce it you can report it to the bug tracker.For information on how to report a bug, see this URL: https://vvld.in/how-to-report-bugs
The link in the help menu was introduced first as a link to the real bug tracker.
The developer got so much reports they have to change it to link to the forum first as most reports are no bugs. 95% was caused by extensions, wrong settings or a broken profile.Cheers, mib
-
@mib2berlin Thanks for info. The bug number is VB-93761.
-
@dude99 Reporting this feature request as a bug does not answer the question. Since the Bug Tracker is closed, one still has no idea when/if a bug will be fixed.
Can we got an answer from vivaldi team if this problem is at least acknowledged?
I did answer the question. Tagging this thread as In Progress would indicate that the team are currently working on it.
If you had reported this as a bug on January 31st, or when you first noticed it, would it be fixed by now? I doubt it, because there are thousands of bug reports, and the Team is still small.
Meanwhile, setting the close tab activation to Active Right in Tab Order would clear any confusion that can arise from Recently Used Order or Related Tab, and makes it simple to activate the previous tab stack by using a shortcut for Previous Tab by Order or by clicking one in the stack.
I do not regard it as a bug if the next tab to the right happens to be outside the tab stack. That is what the setting is designed to do. The request is certainly a valid one, but it will have to wait to be fixed, whether it is regarded as a bug or not.
-
@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.