Closed Bug 167329 Opened 23 years ago Closed 22 years ago

Mozilla doesn't properly set itself as default browser under Jaguar

Categories

(SeaMonkey :: UI Design, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jstock, Assigned: samir_bugzilla)

References

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20020907 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20020907 When attempting to set Mozilla 1.1 as default browser under Jaguar, it can be selected under System Preferences->Web but if you click on a URL it doesn't actually use Mozilla. Going back into System Preferences->Web doesn't show Mozilla 1.1 as the selected browser. In my case it defaults to IE every time. I didn't test to see if this is still an issue in trunk builds, but it works in the latest 1.0.1 build although this issue did crop up with some 1.0.1 builds I've tried previously. Reproducible: Always Steps to Reproduce: 1.System Preferences 2.Web 3.Select Mozilla 1.1 4.Close 5. Click on URL 6. Opens with IE (In my case) not Mozilla 1.1 7. Mozilla 1.1 isn't selected when the web preference pane is reopened. Actual Results: Mozilla 1.1 was not set as the default browser Expected Results: Actually set itself as the default browser
Blocks: 165031
I was able to get Mozilla 1.1 to stick as the default browser by following the suggested workaround in the Chimera 0.5 Release Notes Known Issues section. Namely: removing /Library/Caches/com.apple.LaunchServices.UserCache.csstore and /Library/Caches/com.apple.LaunchServices.LocalCache.csstore and rebooting. I'm still curious why this was needed for 1.1 when the recent 1.0.1 build had no problem changing the default though.
*** Bug 169917 has been marked as a duplicate of this bug. ***
Summary: Mozilla 1.1 Doesn't properly set itself as default browser under Jaguar → Mozilla doesn't properly set itself as default browser under Jaguar
Mozilla 1.1 was my default-browser on X.2 (I don't remember how I did it... I guess it just worked because I updated from 10.1.5 instead of doing a clean install) but now after upgrading to Moz 1.2a I have the same problem described in this bug. Isn't this more or less a OS X 10.2-bug? I change the prefs and they are ignored...
There was an OS bug, fixed in 10.2.2 (or .3) that affects this behavior. Retest; it should work on 10.2.3.
WorksForMe using FizzillaMach/2003021203. Resolving WFM. If you can still reproduce this using a current nightly build on OS X 10.2.3 or newer, feel free to reopen this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.