Open
Bug 526236
Opened 16 years ago
Updated 2 years ago
Test for bug 517396 fails on Linux
Categories
(Core :: Widget: Gtk, defect, P5)
Tracking
()
NEW
People
(Reporter: mstange, Unassigned)
References
Details
Attachments
(1 obsolete file)
This test:
http://hg.mozilla.org/mozilla-central/file/bbbc9c83cdf7/widget/tests/test_bug517396.xul
fails on Linux with the following error message:
7990 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/widget/tests/test_bug517396.xul | moving a maximized window should have changed its width - Didn't expect 994, but got it.
7991 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/widget/tests/test_bug517396.xul | moving a maximized window should have changed its height - Didn't expect 986, but got it.
I'm going to disable it on Linux.
| Reporter | ||
Comment 2•16 years ago
|
||
Are sizemode changes asynchronous on Linux? window.outerWidth apparently doesn't change synchronously after maximize().
Comment 3•16 years ago
|
||
(In reply to comment #2)
> Are sizemode changes asynchronous on Linux? window.outerWidth apparently
> doesn't change synchronously after maximize().
Yes, the app asks the window manager to make the change, and response and notification of response is asynchronous.
The window manager can refuse, but usually they oblige, particularly if the app has focus.
Comment 4•16 years ago
|
||
I'm not sure why an app would want to move a maximized window, but, when using kwin to move maximized windows, they keep their size.
Comment 5•7 years ago
|
||
Priority: -- → P5
Updated•4 years ago
|
Severity: normal → S3
Updated•2 years ago
|
Attachment #9383839 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•