Closed Bug 245532 Opened 20 years ago Closed 20 years ago

Thunderbird sometimes doesn't recognize that it is no longer the default mail client

Categories

(Thunderbird :: Preferences, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Thunderbird1.1

People

(Reporter: mscott, Assigned: mscott)

References

Details

(Keywords: fixed-aviary1.0)

Attachments

(1 file)

If thunderbird was your default mail client and you have turned off the dialog to ask on startup about being the default... You then go through IE / Tools / Options / Programs and change to an old mail client like Netscape 4.x and make if the default. The next time you launch thunderbird we *should* detect that we were the default but no longer are so we should show the dialog once. However old clients like netscape 4.x don't change HKEYCU\Software\Clients\Mail to point to Netscape. We check that registry key first and falsely deduce that we are still the default mail client. So we don't bring up the dialog.
Status: NEW → ASSIGNED
Target Milestone: --- → Thunderbird0.8
Attached patch possible band-aid (deleted) — Splinter Review
fixed on the aviary branch, this patch and several more need eventual migration to the trunk.
Whiteboard: fixed-aviary1.0
Target Milestone: Thunderbird0.8 → Thunderbird0.9
This is not working on today's (9/3/04) "Aviary" branch build.
Flags: blocking-aviary1.0PR?
Flags: blocking-aviary1.0PR? → blocking-aviary1.0PR-
Flags: blocking-aviary1.0?
trix, can you check this out? we think it might be fixed in branch builds.
Flags: blocking-aviary1.0? → blocking-aviary1.0+
I believe this is working correctly on the branch. Still needs to land on the trunk.
Keywords: fixed-aviary1.0
Whiteboard: fixed-aviary1.0
Target Milestone: Thunderbird0.9 → Thunderbird1.1
*** Bug 238567 has been marked as a duplicate of this bug. ***
See also: bug 254262, comment 3 bug 254262, comment 4 and bug 254262, comment 5 These comments are about, seemingly, Thunderbird backing up the registry settings when it sets itself to default, but it was already default, so when you unset it, it still remains default. It should not do anything if it's already set to default.
this has been fixed on the trunk
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
> this has been fixed on the trunk Presumably due to the patch at bug 277833.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: