Open carlosmmatos opened 4 days ago
Hi and thanks for your report
Currently it's possible to navigate to the next tab with ctrl+Tab
and to the previous tab with ctrl+shift+Tab
. As this is nowhere visible to the user, I am opening an internal issue to make this clear to the user.
The issue of similar tab names is also known and is on our roadmap.
Ah, sure enough, that works! Having better guidance would be great. Would appreciate the ability to customize the bindings or perhaps re-thinking what the mapping should be as you formalize it. ctrl + (shift) +tab
is a bit wonky to do with your hands on a laptop. Personally, I would love to see it be mapped to Chrome tab navigation bindings that most everyone is used to — cmd + shift + { / }
As I can see in the official Chrome docs, the default shortcut is ctrl+tab
and ctrl+shift+tab
, at least for windows. On MacOS they are different: cmd+alt+arrow-right
and cmd+alt+arrow-left
. We may change these shortcuts for MacOS.
Great! Thanks very much!
Is your feature request related to a problem? Please describe. Yes, the current method of navigating through multiple open tabs using the mouse is cumbersome and interrupts workflow efficiency. The lack of keyboard shortcuts for tab navigation is a significant usability issue, particularly for users who rely on keyboard commands for speed and productivity.
Describe the solution you'd like Implement keyboard shortcuts to navigate through open tabs, enhancing the user experience. For example, common keybindings on macOS are
Command + ]
andCommand + [
for moving between tabs. This functionality would align with existing keyboard navigation features, such as searching for operations, providing a consistent and streamlined user experience.Describe alternatives you've considered Currently, the only option is to use the mouse to point and click on tabs, which is less efficient and disrupts workflow. No viable keyboard-based alternatives exist within the current implementation.
Additional context Additionally, it might also make sense to add better naming convention to the tabs, or at least let folks have the option to choosing a more descriptive naming convention for tabs. For example, I currently have 4 different GET operations and I couldn't tell you which one is which:![CleanShot 2024-07-02 at 14 43 47@2x](https://github.com/riok/Kreya/assets/64919342/c2dda384-7764-4549-9dfe-60bf4dff54d0)