Closed
Bug 1468082
Opened 6 years ago
Closed 1 year ago
The "Ctrl+Tab cycles through tabs in recently used order" option should also affect closing tabs
Categories
(Firefox :: Tabbed Browser, enhancement, P5)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: fabian.schmied, Unassigned)
References
Details
(Whiteboard: [fidefe-quality-foundation])
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20180516032328
Steps to reproduce:
Enable the "Ctrl+Tab cycles through tabs in recently used order" option to get most recently used (MRU) tab switching behavior
Actual results:
Works for switching tabs, but when I close a tab, the tab to the right of the closed tab is activated, ignoring MRU behavior
Expected results:
The most recently used tab should be activated when another tab is closed
Related support question here: https://support.mozilla.org/en-US/questions/1185889
Comment 1•6 years ago
|
||
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0 (20180611100116)
I have tested this report and I can clearly see the mentioned behavior. When the "Ctrl+Tab cycles through tabs in recently used order" is checked in about:preferences, I can navigate through the recently used tabs. However, it would be great when closing tabs to have the same behavior or order. Currently, when closing a tab, the tab to the right of the closed tab is activated, ignoring MRU behavior.
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
status-firefox60:
--- → affected
status-firefox61:
--- → affected
status-firefox62:
--- → affected
Component: Untriaged → Tabbed Browser
Ever confirmed: true
Reporter | ||
Comment 2•6 years ago
|
||
Just noticed this also affects what tab is activated when another tab is dragged to a new window. It would be great if this also applied the MRU behavior.
Updated•5 years ago
|
Updated•2 years ago
|
Severity: normal → S3
Updated•2 years ago
|
Whiteboard: [fidefe-quality-foundation]
Updated•2 years ago
|
Comment 3•1 year ago
|
||
The UX and product team looked at this and decided not to change anything here.
You need to log in
before you can comment on or make changes to this bug.
Description
•