Closed Bug 310803 Opened 15 years ago Closed 15 years ago
Launching another instance of Seamonkey no longer opens a new tab
This had orignally been taken care of by bug 300485. If you've set your preferences to "open in a new tab", have a browser session open, and launch another instance of Seamonkey - it should just open another tab. (Unless you've specifically used File -> New -> Window.) Something has regressed here since that fix. Now, if I launch another instance, I get another window instead. I'm not sure exactly when this broke, but can try to narrow it down. Using a 10/1 build (and a new profile with tabbed browser preferences set for testing).
Might be a regression of bug 58523, depending on when exactly this broke.
Regression window: Build 9/27 worked, build 9/28 did not. So it's perfectly believable that bug 58523 is the culprit.
(In reply to comment #0) >If you've set your > preferences to "open in a new tab", have a browser session >open, and launch another instance of Seamonkey - it should just open another tab. It depends :-) The new code checks for a -url to open as per preferences (e.g. in a new tab). Failing that, it checks for other specific flags. Failing that, it launches all other parameters specified on the command line. (e.g. -browser or -mail) which always open new windows. Failing that, it launches all windows specified in Appearance preferences, again, always opening new windows. Failing that, your home page opens as per preferences (e.g. in a new tab).
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
Okay. I'm down to your last line: "Failing that, your home page opens as per preferences (e.g. in a new tab)." It doesn't. I click on the Seamonkey browser icon, with no parameters at all, which should only be opening up a browser session - and I get a new window. NOT a new tab as per my preferences. Hence the regression. :) I'm not complaing about how it works with command line switches or mail... (I would expect that to be a new window.)
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
And did you check your appearance preferences?
> And did you check your appearance preferences? I was going to say, yes, it was set to start Seamonkey. Then I thought about it a bit more and what you could be meaning - and unchecked it altogether. Now a new tab opens. So, I agree with you that this is actually INVALID - based on that being what's supposed to happen.
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → INVALID
I guess it's sufficiently confusing to warrent relnoting for SeaMonkey 1.1a
I ran into this same issue. what I did to fix it was to create a backup of seamonkey using mozbackup, then restored that backup. everything worked fine after that.
You need to log in before you can comment on or make changes to this bug.