180327 - Running Turbo twice opens navigator

Status: VERIFIED WORKSFORME

(Core Graveyard :: QuickLaunch (AKA turbo mode), defect)

Description

[John Parsons]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2b) Gecko/20021016
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2b) Gecko/20021016

Because of the difficulties closing down turbo mode I've tried to run it twice
(I only run it when DUN starts) but the second time navigator starts. Surely if
you run turbo twice it should do nothing!

John

Reproducible: Always

Steps to Reproduce:
1.run Turbo with netlaunch
2.Repeat
3.

Actual Results:  
Browser starts

Expected Results:  
Nothing

Comment 1

[Adam Becevello]

I don't really understand the problem that is happening here.
Quicklaunch (Turbo) is designed to speed up load time.  When its on, Mozilla is
already loaded into memory.  If you call quicklaunch again, Mozilla will ignore
it and assume you want to use Mozilla for browsing.  This is the Navigator
window you are seeing.  This should be from the same Mozilla that was quicklaunched.

Unless you are seeing that Mozilla is loading itself twice (ie. 2 separate
processes in the Task manager) then it sounds like Quicklaunch is working
exactly as its suppsed to work.

Comment 2

[John Parsons]

Yes, that is exactly the problem!
Since Turbo mode is only run explicitly with the /turbo switch why assume that
the browser is needed?
If I want the browser I can use the /navigator switch or no switch at all.
Surely the expected and intuitive response if the user opens a program
_in_hidden_mode_ a second time is to do nothing.

John

Comment 3

[Adam Becevello]

You've brought up a good point.

However, on my system (Build ID: 20021114) if I have Mozilla open with a
profile, and then I click on a shortcut that specifically asks for a different
profile on the command line, it will ignore that flag and just load another
navigator.
It seems that the behaviour of Mozilla is if it cannot carry out the option or
it doesn't understand the flag on the command line (try putting something bogus
there), it will ignore it and default to opening Navigator.
If Mozilla follows this behaviour, since it cannot carry out the quicklaunch
option again, its just defaulting to opening Navigator.  That seems to be the
pattern that Mozilla works with stuff like this.
I'm not trying to say that Mozilla works correctly in this case, but it
currently does follow a pattern that is best for most users.  It is impossible
to tell if I shortcut to Mozilla has the -turbo option in it unless you write
that in the name.  If someone forgot they did that, they might wonder why it
doesn't load when they click on the shortcut.

Comment 4

[John Parsons]

I see your point, but I can think of many occasions when such behaviour would be
entirely unexpected. If the user crashes explorer (tray icons disappear) , or in
XP hides the turbo icon they might try to restart turbo mode. If the browser
then pops up it will either try to dial up or throw up error messages.
Besides that the behaviour isn't consistent: try running mozilla.exe /mail when
the mail window is open.

Comment 5

[Adam Becevello]

I personally think the mail window opening again isn't right, there's probably a
bug around here for it, I've just haven't looked yet.

We both seem to have good points for both sides of this.  I guess the real
question here is: what is best for the majority of users (mostly, those that
don't know a lot about computers and the programs they run).
If this question can be answered by someone, then we find out how quicklaunch
should work.

Comment 6

[Grace Bush]

this is working as designed

please see spec at http://www.mozilla.org/xpapps/QuickLaunch/

Comment 7

[Grace Bush]

v

Comment 8

[John Parsons]

Accepting that this isn't a bug but a design issue, is this the place to say
that the design specs don't seem to be logical (to me anyway!)

Comment 9

[Grace Bush]

I think newsgroups are the place to discuss such issues