GNOME Bugzilla – Bug 143145
Clamp windows to screen size on initial map
Last modified: 2006-06-04 16:27:20 UTC
I really thought this bug already existed, but I don't see it. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=83788
Havoc: That page reports that I don't have authorization to look at that bug. Could you post the info from that bug here, or give me perms to look at private rh bugs? ;-)
We already do this. If it's too big for the screen, we auto-maximize and set the saved rect to something like 75% width and height.
Made accessible. You guys might want to confirm it's really fixed.
when do you think it has been fixed ? This bug has been reported 1 month ago: https://bugzilla.ubuntu.com/show_bug.cgi?id=1288 "On a 1024x768 screen, after launching firefox, the window has ~10-20px of the window is hidden under the panel at the bottom of the screen."
Actually the bug is different from what I thought it was.
*** Bug 165197 has been marked as a duplicate of this bug. ***
*** Bug 167538 has been marked as a duplicate of this bug. ***
*** Bug 302210 has been marked as a duplicate of this bug. ***
I have the same bug on Ubuntu Hoary (gnome 2.10). On my laptop wide screen (1280x768), the default firefox window has around 20px of the window hidden under the panel at the bottom of the screen. If I resize and close the window the new size is recorded and the next time I open firefox I get the correct windows size. I can resize the window with ALT+F8 or with a shortcut to vertically maximize the window or moving temporally the bottom panel so I can grab the window's corner, but for a newbye this can become a very annoying problem.
May be worth noting the large d-d-l thread/rant-a-thon on this subject, http://xrl.us/FullyOnscreenRants. In any event, this bug has been fixed on the constraints_experiments branch for some time. :)
[Cue Wizard of Oz music] Ding! Dong! The bug is dead! The wicked bug, The wicked bug, Ding! Dong! The wicked bug is dead...
*** Bug 151839 has been marked as a duplicate of this bug. ***
*** Bug 153506 has been marked as a duplicate of this bug. ***