Open Bug 665700 Opened 15 years ago Updated 15 years ago

Upgrading to SM 2.1 changes link behavior (new tabs)

Categories

(SeaMonkey :: Tabbed Browser, defect)

Product:
SeaMonkey
Component:
Tabbed Browser
Version:
SeaMonkey 2.1 Branch
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

People

(Reporter: dsmutil, Unassigned)

Details

After upgrading from SeaMonkey 2.0.X to 2.1, the default tab option changed from opening in new windows to new tabs. This is likely related to bug 505311, but please don't change the setting for existing profiles. Personally I think the tabs get in the way (I use tabs only when things are very closely related and new windows otherwise) so I would prefer that bug 505311 be backed out, but upgrading shouldn't change the existing settings and way of doing things.
We don't change the settings for existing profiles, if the settings have been changed from the defaults. For settings that are in the default state, the new defaults in SM 2.1 are used. Unfortunately we can't tell the difference between preferences that have never been changed and preferences that just happen to match the defaults.
I see. Well, it's jarring to have the browser change how it works. How about setting the options as the old default if the installer is upgrading a profile but use the new settings for new profiles? Shoot, even the order of the context menu ("Open link in new window" is over new tab in 2.0 and earlier, below afterward) has caught me a few times, but that's the problem with an UI changes.
Problem is the Preferences system only records preferences that aren't the default. And from 2.0 onwards profiles aren't "upgraded" they are used as is. So no migration step is invoked (unlike from 1.x to 2.0). If someone were to write a bunch of code to do this for us we'll certainly look into this, but we are a small team of volunteers and we don't have the manpower to do this *and* do more critical stuff.
I understand about the volunteers, especially for SeaMonkey issues (I've been reporting bugs and triage since at least 2001). I'd still consider this a bug because it creates unexpected behavior but I wouldn't even know how to track what defaults change between versions to know which settings to carry forward and which are completely new.
You need to log in before you can comment on or make changes to this bug.