Closed
Bug 147199
Opened 23 years ago
Closed 23 years ago
Internet Search setting is always reset to "Netscape"
Categories
(SeaMonkey :: Installer, defect)
Tracking
(Not tracked)
People
(Reporter: ken, Assigned: dveditz)
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3)
Gecko/20020523
BuildID: 2002052306
Upon installing a newer build, the Internet Search setting is always reset to
"Netscape", regardless of what I had set it to before.
This setting should be maintained across reinstallations.
I am marking this "Critical" because it is losing data (the value the user had
changed it to).
Reproducible: Always
Steps to Reproduce:
1. Install Mozilla.
2. Change search setting.
3. Install newer version.
4. Search setting is reset to Netscape.
Actual Results: Search setting is reset to Netscape.
Expected Results: Search setting should remain at what I changed it to.
(Note: I just tried to reproduce it in a VM. I installed RC3, changed setting
to Google, then reinstalled. It stayed Google. So I removed it, deleted the
"C:\Program Files\Mozilla" directory, and installed RC2. When I went to change
the setting, it was still Google! But on my main machine, it keeps changing the
setting back, so perhaps it's not reinstall, perhaps it's something else --
maybe this happens after Windows 2000 blue-screens? If that's the case then it
should do a better job of *saving* the settings when the user clicks "OK".)
I've noticed this behavior too, but I am also not sure why it happens or how to
reproduce it. It's not a big deal though, so I don't see why it would be critical.
Reporter: On the machine where you see the bug:
Did you install after uninstalling, or over an older build?
Comment 3•23 years ago
|
||
*** This bug has been marked as a duplicate of 86063 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
R.K.Aa: This machine has had 0.9.7 through RC3 installed, on top of each other.
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•