32540 - Netscape 6 on Mac should have a new creator code.

Status: VERIFIED INVALID

(SeaMonkey :: General, defect, P3)

Description

[Simon Fraser [no longer active]]

Various bugs (see dependencies) result from the fact that Netscape 6 has the same 
creator code ('MOSS') as older verions of the browser. These problems could be 
resolved by using a new creator code. Here are the for/against points that I can 
think of now:

or:

1. No ambiguity as to which version of the browser gets started
   up by the installer/Finder.
2. No desktop database icon weirdness, confusion with 4.x icons.
3. Old utilities will explicitly not work, rather than mysteriously
   fail.

Against:

1. 3rd parties that assume the Netscape is 'MOSS' will have to be
   updated (including the default system IC settings, BBEdit, other
   HTML authoring apps, lots of utils etc).
2. Users will have to explicitly change IC settings to redirect http/https
   urls to Netscape 6 (or the installer will have to update IC settings).

Comment 1

[Simon Fraser [no longer active]]

Another For: you can't run 4.x after launching 6, because 4.x checks for a 
running app with the 'MOSS' creator code 

Comment 2

[Adam]

All of the nightly binaries have a 'MOZZ' creator code (I routinely have both

versions-M15 & 4.72-open or else I couldn't get any work done :-). Is this

different with the builds (haven't compiled in a while).

Comment 3

[Simon Fraser [no longer active]]

Mozilla builds have a 'MOZZ' creator code. Commercial builds use 'MOSS'. This bug 
refers only to the commercial builds.

Comment 4

[Eli Goldberg]

QA Assigning to self.

Comment 5

[J.J. Enser]

Historically, we've seen all major software keep their creator code across 
versions (M$ & Claris suites, BBEdit). However, some others like Stuffit, 
Acrobat, or 4D _have_ changed creator code at some point.

I also think that most Mac users who will decide to install NS 6 (hopefully all 
of 'em ;-) will most likely keep a version 4.x handy, and it would be a Bad Thing 
to force them to open 4.x _first_ in case they want to run both simultaneously.

I am more concerned about the interaction with 'caller' apps if we move away from 
'MOSS'. On one side, there is Apple and Internet Config, together with all the 
apps that rely on IC to launch a browser or pass it a url.
Until they incorporate our new creator code, we can either
1) ask the user and update their system prefs at install time ("à la Microsoft"), 
or
2) document in the Read Me how to do manually make NS6 their default browser, 
mailer, and news reader.

We would also need to address other major publishers that interact with a browser 
but don't rely on IC (Bare Bones?   Adobe?) for them to rev their app - which 
could take a while. Until then, I noticed that in most cases (BBedit, Golive, 
HomePage, VisualPage) it's possible to _manually_ pick any app as your "web 
browser".

My vote goes to change the creator code for the advantages it brings. I can work 
around the disadvantages. It's a one-time setup that hopefully won't put off 
average users.

Comment 6

[Kathleen :Brade]

the sooner we do this the better; sooner will allow more other software packages 
to become aware of the issues and revise themselves as needed.  I would guess 
that most packages would have a minor point release (if not a major one) in the 
next 6 months...

Comment 7

[Kathleen :Brade]

Adding Michael LaGuardia to the cc list since this is related to other decisions 
he is responsible for.

Comment 8

[german]

I am in favor of using something else than MOSS, due to the applescript-lets
that ship with 4.x Mac and the put on the desktop at 4.x install for launching
Mail etc. For the time being a lot of people will use 4.x in parallel to 5.x. It
is disconcerting that the AS now launches a different app, and in some cases
even stops working properly as it inists on launching Seamonkey, but fails with
the specific parameters. People will see this as 'it screwed up my current
installation of Nova to force me to use Seamonkey'.

Comment 9

[Simon Fraser [no longer active]]

M16 these puppies

Comment 10

[Adam]

I think Netscape 6 should have a different creator code. After feedback from the
NS 6 preview release and personal experience, I'd say this would be more than
worth the trouble it might cause. Especially if users are, like you mention,
going to want to use both NS 4.72 and 6 at the same time/on the same computer.

Hey, if Apple can do away with the floppy drive and ADB...

Comment 11

[rubydoo123]

m17

Comment 12

[Simon Fraser [no longer active]]

*If* we do this, it *has* to happen for beta2. This is a very trivial change on 
my part, but the wider ramifications are legion.

Comment 13

[leger]

Putting on [nsbeta2+][6/01] radar.  This work must be done by 06/01 or we may 
pull this for PR2.

ekrock, we need help evangelising developers on this please!

Comment 14

[ekrock's old account (dead)]

I don't know enough about this to have an intelligent opinion or participate in 
deciding what's The Right Thing (and really that's an issue for a Navigator PM 
to consider, not me, anyway), but after those who do have decided, I'll be happy 
to help in evangelizing the info to developers. Just let me know what needs to 
be said and to which audiences (ISVs, users, etc.).

Comment 15

[Simon Fraser [no longer active]]

Erik: I'll come up with some verbage for you, once we've settled on a new code.

Comment 16

[leger]

Due to slip in schedule, moving this bug from [6/01] to [Will be minus on 6/15] 
for fix deadline.

Comment 17

[Simon Fraser [no longer active]]

After much deliberation, we've decided to keep the creator code the same. This 
will avoid problems for naive users who've upgraded to 4.x. More experienced 
users who want to run 4.x and 6.0 at the same time will know enough to work 
around any problems that occur.

Comment 18

[Zach Lipton [:zach]]

Marking verified invalid.