Closed Bug 337061 Opened 18 years ago Closed 17 years ago

middlemouse.contentLoadURL preference is forgotten every time a new version of Firefox is started

Categories

(Firefox :: Settings UI, defect)

1.5.0.x Branch
x86
Linux
defect
Not set
minor

Tracking

()

VERIFIED INCOMPLETE

People

(Reporter: dpn, Unassigned)

Details

(Whiteboard: CLOSEME 06/27)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.3) Gecko/20060507 Firefox/1.5.0.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.3) Gecko/20060507 Firefox/1.5.0.3

I use middlemouse.contentLoadURL quite frequently during my browsing.  Therefore, I have the option turned on.  Ever since Firefox 1.5 every time I upgrade then start the new Firefox version this preference has been changed to "false."  None of my other preferences have been mysteriously reset to default, just this one.  Why is this behavior treated differently?  It is a real pain to reset this option in about:config every time, and goes against the smooth update concept by forcing users to reset their preferences each time they upgrade.

Reproducible: Always

Steps to Reproduce:
1.  Set middlemouse.contentLoadURL to true, exit Firefox
2.  Upgrade installed version of Firefox (even minor upgrades)
3.  Start Firefox

Actual Results:  
middlemouse.contentLoadURL has been reset to false and clicking the middle mouse button no longer achieves the desired result.

Expected Results:  
The user's preferences should not be changed during an update, unless specific circumstances require a change.
Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!
Whiteboard: CLOSEME 06/27
Version: unspecified → 1.5.0.x Branch
No response from reporter re: comment 1 -->INCOMPLETE.
Reporter, if you still see this problem with the latest release of Firefox 2, please reopen this bug. Thanks!
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.