If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Install sets SeaMonkey as default browser

RESOLVED INCOMPLETE

Status

SeaMonkey
General
RESOLVED INCOMPLETE
5 years ago
3 years ago

People

(Reporter: Ric Steinberger, Unassigned)

Tracking

SeaMonkey 2.15 Branch
x86
Mac OS X

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.101 Safari/537.11

Steps to reproduce:

Just allow new version to be installed 


Actual results:

SeaMonkey sets itself to be the default browser, overriding existing system setting.


Expected results:

SeaMonkey should NOT override existing default browser setting.

Comment 1

5 years ago
Hmm, when you launched the new version you should have seen a dialog/sheet asking you if you wanted to set SeaMonkey as the default client (with some options). Are you sure you didn't confirmed it (I'll attach a screenshot so you can see how it looks)?

Comment 2

5 years ago
Created attachment 705090 [details]
Default client sheet

This is how it looks when you get the question wheteher to set SM as the default client.

Comment 3

5 years ago
Ric, please see comment #1.
Flags: needinfo?(ricst)
(Reporter)

Comment 4

5 years ago
Here's what the install program needs to do:

1) Check to see if SeaMonkey is already set to be the default browser.  If it already is, then skip the dialog and leave the setting.
2) If it's not currently set to be the default browser, then skip the dialog and honor that choice.
3) Only if this is a new install should the user be prompted as to whether he/she wishes for SeaMonkey to be the default browser.
Flags: needinfo?(ricst)

Comment 5

5 years ago
We already do 1-3, but:
1) We check for more than just the browser
2) We skip the dialog if you choose so

Comment 6

3 years ago
No reply in more than a year. Closing.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.