Closed
Bug 231799
Opened 22 years ago
Closed 20 years ago
Mozilla always asks to be the default browser when it already is after nightly build upgrade
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: dean, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7a) Gecko/20040121
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7a) Gecko/20040121
After installing mozilla nightly build for the first time it correctly asks to
be the default browser. I click yes, then upon installing a newer nightly build
the next day mozilla then reasks to be the default browser even though it should
already be the default browser as yes was clicked the day before.
Is this the correct behaviour?
Reproducible: Always
Steps to Reproduce:
1.install mozilla
2.make default browser
3.install newer mozilla
4. run mozilla
Actual Results:
it asks to be default browser
Expected Results:
Realised it already was the default browser and not ask upon every upgrade.
Comment 1•22 years ago
|
||
hm, did you install the new nightly into the same directory?
| Reporter | ||
Comment 2•22 years ago
|
||
Yes, everytime i overwrite the old nightly build path just so that nothing
changes between a normal upgrade (i wouldn't usually use 3 different versions
of mozilla stable build) and every time i load the new build for the first time
it asks to be the default browser even though it already is as i chose yes from
the day befores nightly build.
Is this the wanted behaviour??
Updated•21 years ago
|
Product: Browser → Seamonkey
Comment 3•20 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 4•20 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•