Closed Bug 156947 Opened 22 years ago Closed 22 years ago

category menu tree in preferences window does not repond

Categories

(SeaMonkey :: Preferences, defect)

x86
Windows 98
defect
Not set
major

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 135017

People

(Reporter: jamie, Assigned: bugs)

References

()

Details

I open up the Preferences window, under Edit, and it has the first part of te 
Appearance section open.  I can make changes here, but I cannot view (or, 
obviously, change) any other part of the Preferences.
To attempt to clarify:
Inside that white box titled "Category," nothing happens when you click with 
either mouse button.
I have the same problem with the Mail/News Preferences, and with the Mail/News 
folders (where your inbox, trash can, and such are).  With the Mail/News 
folders, the problem is more severe.  The box where the titles of the messages 
should display, and the box where the message itself should display are empty.  
Also, the order of the folders on the left has changed.
Originally, I had e-mail account #1, then account #2, then Local Folders, then 
a newsgroup.  Now, it goes Newsgroup, #1, Local Folders, #2.  This isn't such a 
big deal, but it happened at the same time, and so, might be related.
Likewise, I developed Bug 90337 at the same time.
All of this happened when I upgraded from Moz 0.97 (I think?), to Mozilla 1.0.  
I then upgraded to Mozilla 1.1 Alpha, build 2002061104, in the hopes that these 
had been fixed, but they persisted.
That's all I've noticed so far.  If you want any more information, let me 
know.  Also, if it turns out to be a duplicate of another bug (I did look, but 
there's a lot of these things!

*** This bug has been marked as a duplicate of 135017 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
marking verified as a duplicate.

if you decide to reopen this bug, please clarify why.

search string for bugspam removal: SalviaGuaranitica
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.