Closed Bug 16183 Opened 22 years ago Closed 22 years ago

Pref UI: Category column completely blank

Categories

(SeaMonkey :: Preferences, defect, P1)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: paulmac, Assigned: matt)

Details

If you open up Preferences using 10/12 build, you will see that the Category
section on the left is completely blank. The right side shows up correctly, and
you can in fact click in the left column and change the various panes, so they
are there, but you just can't see them.

Marking as a blocker.

seen on windows/linxu builds 101208
Priority: P3 → P1
Target Milestone: M11
mlum - 10/12/99: 13:04

This bug doesn't happen on WindowsNT (4.0, SP3), with the nightly build from
10/12/99: buildnum: 1999101114.

Open Edit | Preferences.. | ..
The following does occur:

In the Category section of the dialog, there's a legible listing for Appearance,
Navigator, Mail and Newsgroups, Composer, Offline, Advanced, Debug, et. al
Clicking on any of these list items invokes a description window in the right
pane.
It certainly happens on the 1999101208 build on NT 4 SP 5, though...
mlum - 10/12/99 - 13:35

cpratt, can you reproduce this on win98?
backing layout out to 10/11/99 12 noon fixes this,
trying to narrow this down some more.
The same build exhibits the same defect on Windows 98, yes. (I tried a few
different color depths just for the heck of it, and that had no effect.)
Running a windows build with evaughan's recent bug fix, I don't see this problem
on my windows box anymore.

This may have been fixed by his change.
Saw on mcafee linux build that evaughns check in fixed it.
Marking fixed
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
actually, you have to click on resolved fixed to mark it fixed ;-)
Status: RESOLVED → VERIFIED
verified fixed in 101508 builds, all platforms
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.