Bug: Ctrl + Tab does not cycle tabs in recent order
-
And this bug is still with us. It is a biggest issue in Vivaldi at all.
-
We must ensure that this software bug doesn't go unnoticed. I'm on Vivaldi version 6.2.3105.51 (Stable channel) (arm64) and bug still persists.
-
I'm sad that this issue hasn't been addressed in the latest version.
I've posted about this in another thread on this forum, but I wanted to share my observations here as well.
The problem seems to occur randomly when pressing Ctrl + Tab, but it actually appears to be influenced by the timing of the key press.
To reproduce the issue, assign a single key, like F1, to the "Tab Cycler Forward" shortcut.
( you can also enable "Single Key Shortcuts" and choose any single alphabet key. )Then you should be able to reproduce the problem more easily.
For tab history ordered as A, B, C, and D, I expected them to rearrange to B, A, C, D after using the shortcut. However, they shift to B, C, D, A.
Additionally, mapping "Tab Cycler Forward" to a mouse gesture yields the same outcome.
Hope this brings a bit more clarity to the topic.
-
@jon I'd even like to donate to get this bug addressed. Vivaldi is a powerful working tool, I use many of it's features to manage a dozen of projects and it helps me dramatically to get my job done. But this bug is just ruining my work process sometimes.
-
Would not this entire discussion lapse, if the algorithm for the function were published?
(But keep in mind that one definition of "bug" is "an undocumented feature"!)
-
Strange, for me this bug was fixed months ago.
-
@Truemotion I face it every day or two.
-
This bug is really annoying, I run into it all the time, and I'd be willing to make a donation to fix it too.
Ignoring bugs like this, Vivaldi is the best browser. -
What is set here? Try to change
Just realized that it was about Tab Cycler. Which always was in load order, not recent. -
It's not about hotkeys as the bug is not 100% persistent and happens from time to time
-
For me the bug is persistent 100% of the time. Today I've even completely uninstalled Vivaldi, cleaned up all leftovers in ~/Library subfolders and reinstalled it again. And this bug comes back right after I've open first few tabs in my new completely fresh Vivaldi.
Then I've then spend some time experimenting with hotkeys and tab cycler behaviour. To make experiments more visual I've also enabled
Show tab cyclerandDisplay tab cycler as a list. And I've noticed something interesting - when I press Ctrl+Tab time after time slowly, i.e. CTLR+TAB PRESSED -> CYCLER SHOWS -> TAB RELEASED WHILE HOLDING CTRL -> HIGHLIGHTED ENTRY CHANGES -> 1 SEC PAUSE -> CTLR RELEASED OR TAB PRESSED AGAIN, bug never appears. Doesn't matter how many tabs I've changed, it just works and Tab cycler list shows correct tabs order.But! When I repeat this steps quickly, as I used to work with browser, bug appears again almost immediately. In a Tab cycler list it was looked like I accidentally pressed TAB few more times. So I've got a hypothesis that the bug is related to shortcut processing in Vivaldi or in MacOS itself.
So to check hypothesis I've changed
Tab cycle forwardshortcut to CTRL+Q, but bug wasn't resolved. Then I've tried OPT+Q - and it worked! Bug seems to be completely resolved when CTRL key is not used.I had to test it more, and OPT+Q is absolutely UX nightmare I do not want to use, but at least it could possibly lead me to some acceptable workaround.
-
@realscorp wow! Added Opt+Q shortcut, too, and it works like a charm. Thank you for this workaround!
-
I can also confirm the Opt+Q workaround from @realscorp working! Thanks a lot!
It is so unfortunate that this bug exists for a very long time now. The workaround is OK temporarily but really screws up the muscle memory, Vivaldi team please
looking forward to the bugfix.Details: MBP M1 Ventura 13.5 Vivaldi version: 6.4.3160.42 (Stable channel) (arm64)
-
@rromanov, @selimarikan Glad to hear it works for you! Sadly for me I cannot use OPT+Q as all-time workaround, cause my MacOS is printing special symbols when I use OPT+SOME_ALPHABET_KEY combination.
I've spend more time investigating issue. First of all, I've been wrong about what happens when you use CTRL-based shortcuts: when bug occurs, it's not like you virtually pressed shortcut more times than you pressed it actually. Instead last tab somehow get moved down to the tab list. It's visible pretty clear when you have
Show tab cyclerandDisplay tab cycler as a listenabled. Such a pity we don't have source codes to look in.And I've also tried to disable all the CTLR-based combinations in system shortcuts and Vivaldi shortcuts. It had no effect at all. Just like as shutting down all applications like VSCode that could possibly somehow intercept keystrokes.
Right now I'm out of ideas. One need to have access to source codes at least.
-
@realscorp said in Bug: Ctrl + Tab does not cycle tabs in recent order:
Sadly for me I cannot use OPT+Q as all-time workaround, cause my MacOS is printing special symbols when I use OPT+SOME_ALPHABET_KEY combination.
Yes, same, I see œ character getting randomly printed around!
Another thing I noticed about the issue is, if I "wait a bit" while switching tabs with CTRL-shortcuts, the issue disappears, i.e. -> press tab switch shortcut, wait a couple of seconds during tab switcher window is visible, release the key -> everything is fine.
If I switch tabs quickly with the CTRL- shortcut, the issue happens.Instead last tab somehow get moved down to the tab list.
I also confirm this. When issue happens, the tab is moved to the end of the tab list.
Summary & Findings:
- Normally, the issue happens randomly using Control+Tab to switch tabs maybe 1 in 30-40?
- Pressing Control+Tab shortcut faster triggers the issue more often (1 in 10?)
- When this issue happens, if you keep pressing Control+Tab faster, all the consecutive Control+Tab presses cause the issue and send the tabs to the end of the tab list.
- It is way easier to reproduce the issue with "heavier" webpages rather than trying this on speed dial.
- Once the issue starts to happen, Vivaldi goes into a "broken" state for a couple of seconds and issue happens way way more often (1 in 3)
- The issue almost never (1 in 300?) happens if I change the keyboard shortcuts to e.g. Option+Q as realscorp suggested. However, during testing, if Vivaldi gets into this "broken" state, I had the issue with the Option+Q shortcut a couple of times.
- I tried to get some debug logs with
--enable-logging --v=1flag but does not seem to work anymore? - Did not see any error messages in terminal when I started Vivaldi from terminal
- No special errors in Mac
consoleapp/logs
The issue could be due to some event loop/handling and task priorities messing up the input event processing order somehow + a possible off-by-one error in updating the tab list during the tab change event?
Not sure how to ping Vivaldi devs but that's all I can do for investigation @Vivaldi @jon -
@selimarikan Write a bug report, no need to ping anyone. Keep steps simple and try to find a version which triggers the bug most reliably.
-
@luetage Thanks for your suggestion. It has already been reported, investigated, and nothing much happened, that's why we are discussing here to somehow raise awareness to this issue.
This bug has been there for more than a year and it has already been reported many times, additionally:
- Reported VB-95852 by @Truemotion
- @rucker showing a video of the issue
- https://forum.vivaldi.net/topic/80343/cycle-in-recently-used-order-seems-broken
- https://forum.vivaldi.net/topic/80027/mru-loses-my-last-tab-frequently
- https://forum.vivaldi.net/topic/81872/tab-cycling-keeps-malfunctioning
Because the issue is so annoying, I am sure there are some users on the thread, if the source code is provided, would try to debug the issue gladly
As the users, and personally as a supporter from way back Opera times, I believe we did what we could and therefore asking for support from developers and trying to escalate this.
-
@selimarikan Devs don’t read on the forums, they don’t have time. The bug was closed, it’s best to create a new one with the new insights. The point is to issue a bug report that is reproducible—as a prerequisite to getting it fixed eventually. As long as no bug report is confirmed, the issue will remain unresolved.
-
@realscorp @selimarikan I use this layout so Opt+Q luckily triggers nothing more. Might be helpful for you (it has EN layout)
https://ilyabirman.ru/typography-layout/ -
@luetage said in Bug: Ctrl + Tab does not cycle tabs in recent order:
The bug was closed
Well, we are not aware of it because bug tracker is private. This is one more reason we discuss it here as it is possible to get some feedback here.
Ok, I will report a bug, hope @selimarikan will do the same with his findings.
