bugzilla.mozilla.org has resumed normal operation. Attachments prior to 2014 will be unavailable for a few days. This is tracked in Bug 1475801.
Please report any other irregularities here.

turbo pref doesn't work (in one case anyway)

RESOLVED WONTFIX

Status

Core Graveyard
QuickLaunch (AKA turbo mode)
RESOLVED WONTFIX
17 years ago
6 years ago

People

(Reporter: Conrad Carlen (not reading bugmail), Unassigned)

Tracking

Trunk
mozilla1.2alpha
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
1) Have turbo turned and used by mozilla installed in one place
2) Start up a build in another place and turbo does not come on when launched
3) Go to the prefs, the box is checked, click OK for good measure
4) It's still not on

This is probably only an issue for our own builds. Using the installer, users
won't run into this - will they? The reason is that this code:
http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/xpfe/bootstrap/nsNativeAppSupportWin.cpp#647
does not use the same test as this code:
http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/xpfe/components/winhooks/nsWindowsHooks.cpp#529.
That's why resetting it in the prefs has no effect. To work around this, say
switching between one build and another, you have to use "Disable Quicklanch"
and then set it in the prefs.

Comment 1

17 years ago
This was discussed by dp, Sean, myself, and maybe Syd at some point.  There is
only one value under Run and we didn't want *all* Mozilla's to run quicklaunch
when the user turned on the pref in one (i.e., multiple Mozilla processes
running simultaneously).

I think we might still be looking for the ultimate solution to that problem.  We
can probably use this bug to track it.

Adding dp, Sean, and Syd to cc: list; setting target milestone.
Target Milestone: --- → mozilla1.0
(Reporter)

Comment 2

17 years ago
I agree that only one installation should be able to run it at a time.

I think the logic in the first link I gave is right. If
nsWindowsHooks::IsStartupTurboEnabled did the same thing, it would behave as I
would expect - at least the setting in the UI would reflect reality.

Really, IsStartupTurboEnabled is giving the wrong answer.

Comment 3

17 years ago
->mozilla0.9.7
Target Milestone: mozilla1.0 → mozilla0.9.7

Comment 4

17 years ago
Mass moving bugs that won't get fixed this milestone.
Target Milestone: mozilla0.9.7 → mozilla0.9.9

Comment 5

17 years ago
balancing bug lists
Keywords: nsbeta1+
Target Milestone: mozilla0.9.9 → mozilla1.0

Comment 6

17 years ago
-> me

Not sure this needs to be plussed, though. As you said, I don't think users will
run into this too often, unless they install to a different directory (right?)
Assignee: law → blaker

Comment 7

17 years ago
nsbeta1- per ADT triage team, ->1.2
Keywords: nsbeta1+ → nsbeta1-
Target Milestone: mozilla1.0 → mozilla1.2
Assignee: bross2 → quicklaunch
QA Contact: agracebush
Quicklaunch/Turbo Mode is no longer supported in Seamonkey 2 and Seamonkey1.X is in the maintenance mode (fixing only security bugs)
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → WONTFIX
Component: QuickLaunch (AKA turbo mode) → QuickLaunch (AKA turbo mode)
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.