Closed
Bug 294143
Opened 20 years ago
Closed 19 years ago
Cross-platform insonsistency of "open in new tab"
Categories
(SeaMonkey :: UI Design, enhancement)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: belg4mit, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510 On Win32 OiNT does not change focus, on Linux it does. Arguments can be made for either behavior so it should possibly be a setting in the Tabbed Browsing Preferences. Reproducible: Always
Comment 1•20 years ago
|
||
I think the behavior difference you are describing is controlled by: Preferences > Tabbed Browsing > Select new tabs opened from links. (At least with Mozilla Suite Trunk Builds on Windows.)
The preference defaults to the same value on all platforms: http://lxr.mozilla.org/seamonkey/search?string=loadinbackground - are you sure the behavior really is different by default?
Component: General → XP Apps: GUI Features
| Reporter | ||
Comment 3•19 years ago
|
||
Where default is defined as "what I as a user, not having tweaked this seemingly undocumented and inaccessible option, have experienced" yes. Yes I am sure. Although like so much else it seems it may be version dependent. On windows the version who's behavior was reported was the official build I downloaded in early April. On the other hand I just downloaded the craptacular 1.8b2 and it *also* changes focus to new tabs.
| Reporter | ||
Comment 4•19 years ago
|
||
Now that Tilby points it out, I see there is in fact a user control for this behavior. I suppose it is possible I had set it previously, though this seems unlikely since there are other behaviors here that I would definitely have altered had I accessed this preference panel. Anyhow, I suppose this is not a very credible bug report. Carry on (and feel free to redirect your energies to bringing back roaming ;-)
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•