STR: 1. Open a new tab, and go to google.com. 2. Click a link to go to another page, so that the back button is enabled. 3. Cmd+Click on the back button. Expected: Google homepage should be opened in a new tab. Actual: A new tab will be opened with your current page and the same history, the same form contents, etc. Effectively the Cmd+click duplicates the current tab. The same behavior happens on clicking the entries of the context menu of the back/forward button that shows your history items.

Nominating for blocking, as this is a regression from 3.6.

Blocking for regression.

This doesn't seem to be happening anymore (it opens the expected page). Tested on Win/OSX with Cmd and middle clicking. Although the back/forward history is preserved (is this a feature?)

Still experiencing the issue on latest trunk build. It doesn't happen with a new profile but I'm unable to isolate the problem - it happens even in Safe Mode.

you can check on about:support what are your non-default settings, or a more comprehensive list by going to about:config and sorting the table by the status column

Like comment 3, I can't reproduce it any more, but the history list being preserved is still a behavior regression from 3.6.

I've identified the problematic config to be browser.search.useDBForOrder=true

Sorry for the mixup. I'm still unable to identify it.

browser.sessionstore.max_concurrent_tabs=0 causes the issue.

Thanks for investigating, Teoh. The session history being inherited is a feature (bug 448546), so the remaining issue here is the incorrect navigation when max_concurrent_tabs=0

What's happening is that with max_concurrent_tabs=0, gBrowser.duplicateTab leaves tab.linkedBrowser.__SS_restoreState set to TAB_STATE_NEEDS_RESTORE. I'm trying to find why is that happening. when the browser immediately switches to that tab, SessionStoreService.TabSelect is called, and then it restores the tab with the data from the tab it was duplicated from.

Duping to bug 611514 since it has the most recent blocking status set and I'm pretty sure I've found the specific issue (see comment 1 there)

Dao has a patch that should fix this in bug 623893 so duping to that instead.