Closed Bug 580569 Opened 14 years ago Closed 14 years ago

Ctrl/Cmd-Clicking on the Forward/Back Button or Items in Tab History Should Follow Tab Opening Behavior of browser.tabs.insertRelatedAfterCurrent Preference

Categories

(Firefox :: Tabbed Browser, defect)

x86_64
Windows Vista
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 539594

People

(Reporter: tehbaut, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 (.NET CLR 3.5.30729)

Currently, if you Ctrl/Cmd-Click or Middle-Click on the Forward or Back Button, or on Items in Tab History context menu, such new tabs are opened at the end of the tab bar. However, these tabs are ideally related to the current tab because they are from that tab's history. Therefore, it makes sense that they should follow tab opening behavior of the user-settable preference: browser.tabs.insertRelatedAfterCurrent 

Reproducible: Always

Steps to Reproduce:
0. Make sure browser.tabs.insertRelatedAfterCurrent = true (in about:config)
1. Open a tab that has a history
2. Ctrl/Cmd-Click or Middle-Click on that tab's Back Button

Actual Results:  
The new tab is opened at the end of the tab bar, despite the above preference being set to true.

Expected Results:  
The new tab should be opened next to the current tab, since it is related to the current tab.

I'd suggest that when a "Duplicate Tab" functionality is added to Firefox's Tab Context Menu in the future (as per this enhancement request https://bugzilla.mozilla.org/show_bug.cgi?id=455722) that it too follow this same user-settable preference (browser.tabs.insertRelatedAfterCurrent).
Actually, it looks like this is working properly in the latest trunk. Marking as fixed.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Only fixed on trunk by bug 539594.
Resolution: FIXED → DUPLICATE
You need to log in before you can comment on or make changes to this bug.