[Xquartz-dev] Xquartz-dev Digest, Vol 78, Issue 9
René J.V. Bertin
rjvbertin at gmail.com
Sun Mar 22 13:15:42 PDT 2015
On Sunday March 22 2015 12:00:02 xquartz-dev-request at lists.macosforge.org wrote:
> I presume since it is just XQuartz that is seeing this issue that there must
> be *something* I could do put XQuartz in a mode that would prevent this
> focus loss, but I'm at a loss to know what that is because I have no idea
> why the focus is being allowed to be stolen in the first place.
Let's see how wide open the door is I'm about to kick in :)
I think that what happens is that some application starts in a way that it becomes the front application (is it (still) possible to launch an app through LaunchServices without that happening?). It, or the OS returns focus to the application that had it (which is something that could be done so quickly that there's very little chance anything gets lost). Normally, someone would know what window was the key window in that application, but X11 must be different. Either no window gets focus, or the wrong window.
Myself I've never seen this happening, and I spend a lot of time in XTerms. I wonder if the reason is that I never use QuartzWM but something more traditional (recently migrated from ctwm 3.5 to xfmw4 4.11.2). If that's the case though, my explanation above cannot hold, or at least I don't see how. I can't imagine that a legacy WM like ctwm is prepared to restore focus after the X11 server lost and regained focus, it's author likely never dreamt such a thing would even be possible :)
I *am* seeing another undesirable behaviour since updating from OS X 10.6.8 to 10.9 . I'm running rooted, and up to 10.6 I could bring 1 xterm to the front and have the others hidden behind native windows. Very practical if you're keeping a native browser window open for reference, for instance.
This is still possible, but periodically all X windows will pop to the foreground. The reverse also happens. It's as if certain events cause the application belonging to the key window to be brought to the foreground - and that could actually be the same event in which others lose their X11 input focus.
Hope this helps in some way...
More information about the Xquartz-dev