Open
Bug 581863
Opened 13 years ago
Updated 8 months ago
gtk/nsWindow::GetScreenBounds returns client window size instead of outer (frame) size
Categories
(Core :: Widget: Gtk, defect, P3)
Tracking
()
REOPENED
People
(Reporter: karlt, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: tpi:-)
nsIWidget::GetScreenBounds should return the "widget's outside dimensions in global coordinates. This includes any title bar on the window." Correcting this will make test_screenPersistence.xul at least correctly notice that windows created with outer dimensions have the wrong size. test_screenPersistance.xul will also fail because it opens a window with (inner, I assume) width/height = 300 and expects outerWidth/outerHeight to be 300.
Reporter | ||
Comment 1•13 years ago
|
||
gdk_window_get_frame_extents is the function to use here.
Reporter | ||
Comment 2•13 years ago
|
||
(In reply to comment #0) > Correcting this will make test_screenPersistence.xul at least correctly notice > that windows created with outer dimensions have the wrong size. Filed Bug 581866.
Updated•12 years ago
|
Assignee: nobody → diogo.gmt
Updated•7 years ago
|
Whiteboard: tpi:-
![]() |
||
Comment 3•5 years ago
|
||
Closing GTK2 related bugs since we removed GTK2 support at the beginning of 2018 in bug 1278282. Probably best to open a new bug in the unlikely event that any of these are still relevant.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
Reporter | ||
Updated•5 years ago
|
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Summary: gtk2/nsWindow::GetScreenBounds returns client window size instead of outer (frame) size → gtk/nsWindow::GetScreenBounds returns client window size instead of outer (frame) size
Comment 4•1 year ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months.
:stransky, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee: diogo.gmt → nobody
Flags: needinfo?(stransky)
Updated•1 year ago
|
Updated•8 months ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•