Chrome's native tab navigation (Ctrl+Tab) skips over collapsed tab groups - you can only navigate to visible tabs. Vimium's J/K currently navigates into collapsed groups, which feels inconsistent.
I have a working implementation locally that makes J/K skip collapsed groups (using the tabGroups API). Before submitting a PR, I wanted to check:
- Is this desired behavior? Or do some users prefer being able to navigate into collapsed groups?
- Should it be configurable? e.g., a setting or command option like
map K nextTab skipCollapsed
- Are tests needed? The change is ~25 lines and affects
nextTab/previousTab/firstTab/lastTab.
Note: This would add the tabGroups permission (no new user-facing warnings). Firefox behavior would be unchanged since it doesn't support tab groups.
Happy to submit a PR if there's interest.
Chrome's native tab navigation (Ctrl+Tab) skips over collapsed tab groups - you can only navigate to visible tabs. Vimium's J/K currently navigates into collapsed groups, which feels inconsistent.
I have a working implementation locally that makes J/K skip collapsed groups (using the
tabGroupsAPI). Before submitting a PR, I wanted to check:map K nextTab skipCollapsednextTab/previousTab/firstTab/lastTab.Note: This would add the
tabGroupspermission (no new user-facing warnings). Firefox behavior would be unchanged since it doesn't support tab groups.Happy to submit a PR if there's interest.