Closed Bug 148660 Opened 22 years ago Closed 22 years ago

bouncing windows effect (bug 120155) still appears with certain websites

Categories

(Core :: XUL, defect)

x86
Windows 98
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 120155

People

(Reporter: wbrenne, Assigned: jag+mozilla)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; de-AT; rv:1.0rc1) Gecko/20020417
BuildID:    2002041711
Theme: Classic, don't know about modern

The well-known "bouncing windows" effect is only partly resolved. While viewing
pages like http://dpa.mbt.zet.net/ticker.html or
http://www.mozilla.org/quality/help/bugzilla-helper.html the attepmt to minimize
will result in the window bouncing again.
A walkaround is to open the mailnews window and to close it again; after that
the browser window behaves normal. This walkaround helps sometimes, but not
always (without any obvious rule).
The browser can't be released with this, really!

Reproducible: Always; from step 5 on: Sometimes
Steps to Reproduce:
1. open two (or more) browser windows, all maximized
2. browse to http://dpa.mbt.zet.net/ticker.html in one window
3. try to minimize both browser windows in any order
4. result: the youngest window will pop up.
5. restore all browser windows
6. open mailnews window and close it again
7. try to minimize both browser windows

Actual Results:  Windows behave like they should, even if you reload the page.

Expected Results:  The browser windows should ALWAYS minimize on minimize commands.

NOTE: When you don't restore all browser windows in step 5, opening and closing
the mailnews window won't help!

*** This bug has been marked as a duplicate of 120155 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
New fashion to resubmit all old bugs?

pi
Status: RESOLVED → VERIFIED
Reporter, you should update your build, not only for fixing this bug, but also
for security reasons. (Plus, the bug reporting guidelines say that reporting
bugs with old builds is pointless, and rightly so.)
You need to log in before you can comment on or make changes to this bug.