Closed Bug 90858 Opened 23 years ago Closed 23 years ago

Selecting the Font then selecting another pref item locks you in that pref item

Categories

(SeaMonkey :: Preferences, defect)

x86
Windows 98
defect
Not set
major

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: dereks, Assigned: samir_bugzilla)

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.2+) Gecko/20010711
BuildID:    2001071104

If you select Fonts in prefs then select another pref item (anything but Fonts)
you will be locked in the pref item you just selected

Reproducible: Always
Steps to Reproduce:
1. Goto Edit->Prefs
2. Select Fonts
3. Select another pref item
4. Select another pref item

Actual Results:  You should be locked in that pref item

Expected Results:  Changed to the selected pref item
You can switch between Fonts and Themes without being locked in either
WFM windows 98 2001-07-15-08-0.9.2
Reproducible for me with 2001071104/WinNT, will have to test with a later build 
when I get one though...
Following error appears in Javascript console:

Error: document.getElementById(lists[i]) has no properties
Source File: 
chrome://communicator/content/pref/pref-fonts.js
Line: 55

This bug appears to have gone away in 2001071408 Win98
marking wfm per reporter's last comment.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
mass verification of WorksForMe bugs: to find all bugspam pertaining to this,
set your search string to "IfItWorksForSlappyTheSquirrelThenItWFM".

if you think this particular bug is *still* an open issue, please make sure of
the following before reopening:

a. that it's still a problem with ***recent trunk builds*** on the all
appropriate platform[s]

b. provide clear steps to reproduce (unless a good test case is already in the
bug report), making sure it pertains to the original problem (avoid morphing as
much as possible :)
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.