Closed Bug 13316 Opened 25 years ago Closed 25 years ago

Strings prefs in preference panel are broken

Categories

(SeaMonkey :: Preferences, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: morse, Assigned: matt)

Details

Go to preference panel.  Select any string valued preference.  The two I tried
are Navigator/Homepage and Advanced/Server-for-wallet.  Enter a string in the
text box.  Press OK.

The string you entered does not appear in the prefs.js file although other
preferences from the same pane have been added.  If you return to the preference
panel, the string you entered is not displayed.

Finally, there is an initial value for the Advanced/Server-for-wallet string
that I specified in all.js.  Namely it should have the value of
http://people.netscape.com/morse/wallet/.  And, indeed, the execution of the
wallet code is picking up and using that value.  But the text displayed in the
advanced-preference panel for this string is blank.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
fixed
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Clearing FIXED resolution due to reopen.  matt, why did you reopen?
I'm guessing that it was reopened as making changes to string pref such as Home
page crashes when you click OK. Matt?
It was actually reopened because I called Matt and told him that the
advanced/wallet-server string pref still wasn't working.
Status: REOPENED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → FIXED
This should work now.
fixed
I can't get the homepage to crash
on windows or linux.  I tried it on mcafees machine also.
i filed 13499 which might be related to the crash
Status: RESOLVED → VERIFIED
As of the 19991008xx builds, setting the home page pref (for example) both works
and doesn't crash. Marking verified using the 1999101908 build, NT.
Bulk move of all Pref UI component bugs to new Preferences component.  Pref UI 
component will be deleted.
Component: Pref UI → Preferences
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.