After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 513946 - maximized windows do not get get raised when you click on the bottom border
maximized windows do not get get raised when you click on the bottom border
Status: RESOLVED OBSOLETE
Product: metacity
Classification: Other
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2008-02-02 20:07 UTC by Sebastian Keller
Modified: 2020-11-06 20:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Log of the raise problem (211.93 KB, application/octet-stream)
2008-04-13 14:16 UTC, Sebastian Keller
  Details
frames: raise maximized window if clicked on border (2.58 KB, patch)
2017-09-29 22:49 UTC, Alberts Muktupāvels
none Details | Review

Description Sebastian Keller 2008-02-02 20:07:22 UTC
Please describe the problem:
When clicking at the bottom border of a maximized window it gets focused, but not raised.

Steps to reproduce:
1. Make sure you have no panels at the bottom
2. Maximize a window
3. Focus and raise a non-maximized window
4. Move the cursor to the bottom of the screen
5. Click at the bottom border of the maximized window


Actual results:
The window gets the focus, but it does not get raised.

Expected results:
The window should get the focus and be raised

Does this happen every time?
Yes

Other information:
gconf-settings:
auto_raise = true
auto_raise_delay = 500
focus_mode = click
focus_new_windows = smart
raise_on_click = true
theme = clearlooks
compositing_manager = false
reduced_ressources = false
disable_workarounds = false
Comment 1 Thomas Thurman 2008-03-23 03:21:04 UTC
Confirmed.  Spooky.  Will investigate.

Gnome-love: first step is to reproduce this and attach a log.  If not, I'll deal later.
Comment 2 Baptiste Mille-Mathias 2008-04-13 13:12:32 UTC
Sebastien, 

could you try to reproduce the problem to help to fix it ?

Open a terminal and type the following
METACITY_VERBOSE=1 METACITY_USE_LOGFILE=1 metacity --replace

once the problem generated in the log, go back in the terminal and press Ctrl+C which will restart the normal metacity.

then attach here the log file generated, it should be under /tmp, the full path is indicated when the debuf session of metacity is started.

Thanks
Comment 3 Sebastian Keller 2008-04-13 14:16:37 UTC
Created attachment 109173 [details]
Log of the raise problem

I actually created a log-file some weeks ago, but somehow managed to forget to upload it here ;)

But now here it is.

The fullscreen window is Epiphany (browsing metacity-blog, because it is really hard to remember those debug-vars ;), it is called "...for the" in the log.
The other window is the terminal, which is called "sebastian@".
The click on the frame of the Epiphany window is at line 3333 if I read the log correctly.
Comment 4 Sebastian Keller 2008-05-01 03:47:12 UTC
I think i found the problem.
There is no specific frame-control for this area. So get_control in meta_frames_button_press_event returns META_FRAME_CONTROL_NONE. This value for control is not handled in this function.
META_FRAME_CONTROL_TITLE which is when click on the title-bar gets raised, because it calls meta_core_begin_grab_op, which calls meta_display_begin_grab_op, which calls meta_window_raise.

Would it be enough to handle (button == 1  && control == META_FRAME_CONTROL_NONE) in meta_frames_button_press_event or should that area become a new frame-control?
Comment 5 Alberts Muktupāvels 2017-09-29 22:49:05 UTC
Created attachment 360687 [details] [review]
frames: raise maximized window if clicked on border
Comment 6 André Klapper 2020-11-06 20:07:28 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/metacity/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.