1707514 - "Move tab" keyboard shortcuts should move all multiselected tabs, like the "move tab to end" commands do

Status: NEW

(Firefox :: Tabbed Browser, defect)

Description

[Shane Hughes [:aminomancer]]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:90.0) Gecko/20100101 Firefox/90.0

Steps to reproduce:

• Select multiple tabs e.g. by ctrl/shift+clicking a range of tabs.
• Right click the tabs, "Move Tabs" > "Move to End". Or, focus the tab bar by focusing the urlbar and hitting shift+tab until the selected tab has visible focus. Then hit ctrl + shift + home.
• Now use the "move tab left" keyboard shortcut ctrl+shift+pageUp.

Actual results:

• When using the "move tabs to start/end" hotkeys, all multiselected tabs are moved.
• When using the "move tabs left/right" hotkeys, only the selected tab is moved.
• I'm almost positive it wasn't like this some months ago.

Expected results:

• The inconsistency doesn't make sense. It's also inconsistent with the dragging + dropping behavior, which moves all multiselected tabs.
• The built-in hotkeys should be changed so these methods move all multiselected tabs, but the functions available to the webextensions tabs API should also be changed in the same way. For example I use an extension Move Tabs Hotkeys which adds similar hotkeys. I use that because it lets tabs wrap around to the beginning. So if the tab is already at the end and I hit the hotkey to move it to the right, it'll move it to the start.
• Personally I think the built-in hotkey should do this too, rather than simply doing nothing if the tab is at the start/end position. But either way, the webextension API methods should be consistent with the internal methods so ideally that would be updated too.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Firefox::Address Bar' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 2

[Negritas Sergiu, Desktop QA]

Hello! I have managed to reproduce the issue using Fx 89.0a1 (2021-04-13), 89.0b10 (64-bit) and 90.0a1 (2021-05-11) on Ubuntu 20. I will update the flags and the set this issue to new in order to get the developers involved.
I managed to reproduce this issue with fx 86.0 this doesn't seem like a recent regression.

Thank you!