Seen in Mozilla/5.0 (X11; Linux i686; rv:7.0.1) Gecko/20110928 Firefox/7.0.1 SeaMonkey/2.4.1 Steps to reproduce: 1) Bookmark two sites in the bookmarks toolbar, one relatively slow loading. 2) Open new tab (ctrl-t) 3) Click on the bookmark for the relatively slow loading site. Observe it starting to load in the current (empty) tab. 4) White the status bar still says "Waiting for ..." middle-click on the other bookmark. Expected: This other bookmarks opens in a new tab. Actual: This other bookmark loads in the current tab, throwing away the previous load.
Confirmed. Mozilla/5.0 (Windows NT 5.1; rv:9.0a2) Gecko/20111102 Firefox/9.0a2 SeaMonkey/2.6a2 I used: (slow) http://www.google.com/search?num=100&hl=en&newwindow=1&q=site%3Akb.mozillazine.org+-intitle%3Atalk+-inurl:%22/index.php?title=%22+-inurl%3A%22%2Findex.php%3Ftitle%3D%22+%S&btnG=Search (faster) http://www.theonion.com/ Reproducing may rely on "no" windows being open <in the window, if that makes sense>. 1. set Browser -> Display on -> New Window => Blank page. 2. open New Window 3. open Sidebar 4. center-click the two links What happens is that the first link opens in the current window rather then in a new tab. And then the second link proceeds to do the same. Center-clicking the links, you would expect both to open in new tabs in the current window. After any window has loaded, subsequent attempts to recreate fail (IOW, at that point, the clicked links do open in new tabs as expected).
Firefox 8.0 works as expected, best I can tell given the differences in how it operates compared to SeaMonkey. 1. Tools | Options | General -> Startup -> When Firefox starts -> Show a blank page 2. open new Window 3. open Sidebar 4. center-click the two links Results: Windows with 3 tabs. about:blank, mozillazine, theonion
Confirming issue still present in current nightly on links from Comment 1 User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/18.0 Firefox/18.0 SeaMonkey/2.15a1 Build identifier: 20120921003032
Hardware: x86 → All
Whiteboard: [2012 Fall Equinox]
Seems to be still present in Seamonkey 2.46.
You need to log in before you can comment on or make changes to this bug.