-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tab MRU order doesn't regard multiple skips #18286
Comments
I made a video about the bug, comparing Brave with Firefox: |
So as I see it's still not done, and it's really critical for me to be productive, so was looking for this issue. @guifel @simonhong any chance it can be fixed? (tagging you since I see you were working on the implementation of the feature in #913) 🙏 |
I also noticed this also, and it kind of makes the feature worse than not having it at all, unfurtunately. As much as I appreciate the work that went into implementing this. |
Let me bump this issue again (hoping that doing that once or twice per year isn't too annoying). I love the Brave browser, I really do. But a browser without the native MRU implementation still sucks for me; I have to use this Chrome extension, which is better than nothing and better than Brave's broken MRU support, but being just a Chrome extension, it has to use a few workarounds, which don't always work flawlessly. Any chance we can get it fixed in Brave so that we'll have a properly working MRU? Feels like we're so close! 🙏 |
I had trouble understanding the issue from the description alone, I am posting new reproduction and results sections to make the bug more understandable. Steps to Reproduce
Actual result:start on tab 1 Expected result:start on tab 1 The difference is the last ctrl-tab, where the expected result is tab 1 (the last tab the user interacted with), but the real result is tab 2 (the tab the user passed by when going to tab 3) Additional Notes:This expected result matches the behavior of shift-tab in Windows and ctrl-tab in Firefox. |
FYI: This issue would be solved by #33693 |
Thanks for adding a better description Lincoln.
Thanks for that link too. While I can see that implementing this preview will likely come together with fixing the MRU behavior, let me share those two thoughts:
I don't know if that preview feature is being considered for the near future work; doesn't seem like it, since it says "Untriaged backlog". So I'd say, if both features are just sitting in the backlog, then it'd make more sense to focus on fixing the MRU first (given the two datapoints I shared above). Lmk if I'm missing something. |
I'm having the same issue myself. I ended up disabling the feature and installed this extension (CLUT). The keybinding is Alt-W instead of Ctrl-Tab, but it works as a temporary workaround. |
Description
Pressing Ctrl+Tab doesn't support skipping to more than the directly single previous tab. Pressing it multiple times always goes back one tab. Very much not like Alt+Tab does in Windows or how Ctrl+Tab works everywhere else.
Steps to Reproduce
Actual result:
Tab active as before pressing Tab the last time in step 3
Expected result:
Should move back to the tab that was active when pressing the Ctrl key in step 2
Reproduces how often:
Easily reproduced
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
The text was updated successfully, but these errors were encountered: