Closed Bug 306329 Opened 19 years ago Closed 19 years ago

Latest SeaMonkey nightlies lose scroll bars (in general, including in Mail) in some themes.

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 222654

People

(Reporter: TheMillers, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050828 SeaMonkey/1.1a
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050828 SeaMonkey/1.1a

I updated my Seamonkey nightly release from 050808 to 050825, but found the
scroll bars had all disappeared! Same after update to 050828. However, it
depends on the THEME in use: I'd been using Toy Factory, which loses scroll
bars. Classic and Modern do not. When I change theme and reload Seamonkey, this
behavior is repeatable. (It does NOT appear to be Bug# 233378.)   

Reproducible: Always

Steps to Reproduce:
1. Select Toy Factory theme.
2. Exit, reload Seamonkey.
3. Scroll bars in Mail, et al, fail to appear!

Actual Results:  
No scrollbars (or scroll buttons) visible -- and they don't work when I assume
they're there but invisible.

Expected Results:  
Normal scrollbar view and action, as when using Classic or Modern themes -- and
as in Toy Factory theme, through Seamonkey nightly 050808; bad behavior appeared
upon update to 050825 and 050828.

I don't know which other themes are affected, but I couldn't do work effectively
in Toy Factory -- my blundering created errors in the mail files themselves.  (I
was able to restore the files, but many users would lose data.)

*** This bug has been marked as a duplicate of 222654 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Summary: Latest Seamonkey nightlies lose scroll bars (in general, including in Mail) in some themes. → Latest SeaMonkey nightlies lose scroll bars (in general, including in Mail) in some themes.
Whiteboard: DUPEME
See also Bug 305391.
Version: unspecified → Trunk
You need to log in before you can comment on or make changes to this bug.