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 669139 - raise_on_click=false is ignored if focus_mode=click
raise_on_click=false is ignored if focus_mode=click
Status: RESOLVED FIXED
Product: mutter
Classification: Core
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2012-01-31 22:08 UTC by Tom Jaeger
Modified: 2014-12-29 06:38 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
fix (1.42 KB, patch)
2012-09-25 20:49 UTC, Tom Jaeger
none Details | Review
Update docs for org.gnome.desktop.wm.preferences.raise-on-click (3.06 KB, patch)
2012-09-26 19:58 UTC, Federico Mena Quintero
none Details | Review

Description Tom Jaeger 2012-01-31 22:08:08 UTC
Apparently this was introduced as a result of

https://bugzilla.gnome.org/show_bug.cgi?id=326156

From what I can piece together after all these years, it seems that disabling raise_on_click was advocated as a workaround for some bug in a pager application, which ired some gnome developers so much that they wanted take away the option from everybody but there was enough backlash from people that used a focus follows mouse policy for them to make an exception in this case.  There was also the issue that raise_on_click was implemented incorrectly as raise_on_activate for a long time, luckily the (trivial) fix for this issue has been applied since.

Now, there is no technical reason for disallowing raise-on-click for a click-to-focus, in fact this is what a lot of people (myself included) prefer.  It seems cruel to take away this option based on some petty politics that nobody can remember anyway.

I've been using the attached patch for a while now and I can discern any adverse consequences so for (and extensive copy-and-pasting a lot won't raise my blood pressure anymore).

The same patch presumably applies to metacity as well, but I have not tested it.  Something should also be done about the description of the raise_on_click gconf key, which is mostly incorrect and mildly insulting right now.
Comment 1 Tom Jaeger 2012-09-25 20:49:28 UTC
Created attachment 225178 [details] [review]
fix

Hmm, looks like I never actually attached the patch...
Comment 2 Federico Mena Quintero 2012-09-25 22:22:39 UTC
I can confirm that Tom's patch works correctly.

TL;DR - raise-on-click doesn't work correctly with click-to-focus, and the patch seems to fix it.
Comment 3 Federico Mena Quintero 2012-09-26 19:58:22 UTC
Created attachment 225232 [details] [review]
Update docs for org.gnome.desktop.wm.preferences.raise-on-click

Now that this is fixed in mutter via https://bugzilla.gnome.org/show_bug.cgi?id=669139,
it no longer makes sense to talk about old bugs or inconsistencies when raise-on-click
is turned off.  We simply describe what the option does.
Comment 4 Federico Mena Quintero 2012-09-26 19:58:57 UTC
The previous patch is for gsettings-desktop-schemas, BTW.  It just updates the docs for the configuration key.
Comment 5 Tony Houghton 2014-01-26 17:41:18 UTC
I agree wholeheartedly with what Tom Jaeger said in the description. I used to prefer sloppy focus so I didn't care all that much, but now I'd rather use click to focus. Please can the patch be adopted.

I'm not entirely sure about the status of mutter wrt gnome-shell though. I use the latter, so should I open a new bug for it? Or are they built from the same code so that a bugrep for one automatically applies to the other?
Comment 6 Jasper St. Pierre (not reading bugmail) 2014-12-29 06:38:27 UTC
https://git.gnome.org/browse/mutter/commit/?id=93b7137c62810460d65acaeab20cb08973d370b5