Red Hat Bugzilla – Bug 150685
RFE: add option to disable metacity's raise-on-click behavior
Last modified: 2007-11-30 17:11:01 EST
Description of problem:
I'm a relatively new metacity user (been using sawfish for a long time, and
before that...uh... fvwm). I like pointer focus, and I'm finding metacity's
raise-on-click behavior (raise a window whenever you click anywhere in it) quite
infuriating. I like to stack my windows, and still be able to click inside
lower-stacked windows without them popping to the front.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set your metacity focus mode to pointer focus.
2. Cascade some windows so that one is below the other and partially obscured by it.
3. Single-click (a simple press will suffice, actually) the window lower in the
The lower window is automatically raised.
There should be an option at least in gconf
(/apps/metacity/general/raise_on_click perhaps) to make it so that the lower
window would not be raised on the click.
I've looked at some of the discussions in old mailing lists and the upstream
gnome bugzilla (bug 76672) for this, and it looks like Havic and the gnome folks
are happy leaving this option out. However, I think there are many like myself
who would like to be able to disable this behavior, and I therefore request that
Fedora add this functionality to its build of metacity.
I've seen a suggested patch for this at
I'm sure it's quite doable. If I have time, I might even try porting that to the
current metacity build.
Created attachment 112159 [details]
Simple patch to disable raise-on-click when in mouse/sloppy focus
I discovered that Havoc put in a conditional to control this behaviour and then
commented it out. I uncommented out. My vote is for raise on click to be
disabled by default when in mouse or sloppy focus mode, regardless of if there
is a gconf option to control this.
For things of this nature, we like to stick to whatever upstream does. Could
you re-file this bug upstream at bugzilla.gnome.org and post a comment here with
the URL to the upstream bug report?
This bug is being closed because it has been in the NEEDINFO state for a long
time now. Feel free to reopen the bug report if the problem still happens for
you and you can provide any information that was requested.