Preferences are not saved

RESOLVED WONTFIX

Status

--
major
RESOLVED WONTFIX
15 years ago
15 years ago

People

(Reporter: Blancjb, Assigned: mikepinkerton)

Tracking

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5a) Gecko/20030610 Camino/0.7+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5a) Gecko/20030610 Camino/0.7+

Changes in preferences are not saved upon closing of application.  Preferences
are reverted to default when the application is launched.  Preferences changes
are effective as long as the application stay open.

Reproducible: Always

Steps to Reproduce:
1.open preferences panel and change history remember value to 1 
2.Close Camino
3.Launch Camino

Actual Results:  
Preference was reverted to default value (=9)

Expected Results:  
preference should have kept the new value (=1)

This is the case for EVERY preference
-> Camino
Assignee: ben → saari
Component: Preferences → General
Product: Browser → Camino
QA Contact: sairuh → winnie
Version: Trunk → unspecified
(Assignee)

Comment 2

15 years ago
is your home dir on a remote server?
Assignee: saari → pinkerton

Comment 3

15 years ago
Confirmed with Camino build 2003081002. I only tested with the History value, but it is not saved 
unless you (a) hit return, or (b) switch to another tab in the preferences window before quitting. 
Simply typing in a new value and closing the preferences window does not save it. However, 
opening the preferences window again after doing so, and going back to the history tab, shows the 
correct value and also causes it to be saved. (This is probably linked to the "changing tabs causes 
value to be saved" behaviour, as you have to change tabs to get back to the history preference. But 
it does tell us that the changed value is preserved in RAM but not written to disk.)
(Assignee)

Comment 4

15 years ago
doesn't happen with "every pref" only the one listed. the analysis is correct.
however we're prolly gonna remove this textfield anyway (it's pretty useless) so
no real need to fix it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.