Closed Bug 116485 Opened 23 years ago Closed 23 years ago

Can't minimise after changing themes

Categories

(Core Graveyard :: Skinability, defect)

x86
Windows 98
defect
Not set
major

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: d_king, Assigned: hewitt)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.7+) Gecko/20011220
BuildID:    2001122003

After changing Theme (View-ApplyTheme) the minimise button (top right of screen)
causes windows to quickly minimise and then restore. The Close button works.
Note: this happens when changing from Modern to Modern as well.

Reproducible: Always
Steps to Reproduce:
1. Open Mozilla
2. Change theme from View Menu
3. Select Apply Theme
4. Choose theme

Expected Results:  Expected Minimise to minimise the open window.
Just downloaded 0.9.7 (2001122106) and I notice that View-ApplyTheme has
reverted back to changing theme on restart.

As I don't fully understand the relationship between the Trunk (where I first
noticed the probem) and the Branch (where I just tested with 0.9.7) I can't
really comment on if this has been fixed or not.
I've just retested this using build 2001122703, and the problem is back again.

The first time I tried, Mozilla crashed (TB987360Q) but this may be related to
other activity that I did before I tried to change themes.
Just retested using build 2002010403, and the problem is still there.

However, subtle change in result. Before, when attempting to minimise a full
screen window, it would come back immediately as a full screen window. Now, it
comes back as a partial screen window.

Any progress in fixing this for good?
Component: Themes → Skinability
http://bugzilla.mozilla.org/show_bug.cgi?id=113043

this bug sticks out in the bonsai query for the 12/19 into the 12-20 build.

http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=SeaMonkeyAll&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=12%2F19%2F01+08%3A00&maxdate=12%2F20%2F01+17%3A00&cvsroot=%2Fcvsroot

I'll do some testing here with older builds I have to see if I see this too, or
if this when bug 120155 started, or maybe it was fixed, or wallpapered, and then
bug 120155 started in build 1/6.

I notice this is fixed. I'm not sure when that happened, but when I tested with
build 2002022203 it works fine.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
wfm, also based on david's comment#5, this is fixed for him.
Status: RESOLVED → VERIFIED
wfm, also based on david's comment#5, this is fixed for him.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.