[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwin
Subject:    [Bug 187718] Focus screwed up after closing emacsclient window (with
From:       Alain Knaff <kde () kde ! lka ! org ! lu>
Date:       2010-06-02 12:17:17
Message-ID: 20100602121717.46E3C43360 () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=187718





--- Comment #3 from Alain Knaff <kde kde lka org lu>  2010-06-02 14:17:14 ---
This is interesting.

But does this work with "exceptions". Say, I set "Focus Stealing Prevention" to
"Extreme" for every window, but want to make an exception for the "Window List"
Widget where it would be "Medium" instead. Would the system correctly know that
the exception should override the general rule?

And btw, how do I find out the relevant window class/role/type for the "Window
List" widget? As this isn't an application with a window, I can't just click on
its titlebar and go into Advanced->SpecialApplicationSettings...

Interestingly enough, other plasma widgets, such as the pager and the taskbar
do work correctly even with "focus stealing prevention" set to "Extreme"
globally!


In the meantime, I did some additional research and found that:
- firefox is affected as well, and in a much worse way, because it can be
triggered by a web page by just popping up a javascript alert()! This has the
advantage of being much easier to debug (no need to restart firefox, just load
a webpage which pops up an alert in a setTimeout() handler instead)
- using xmon, I tried to debug the X message exchanges between Firefox and the
X server, and I suspect that the problem happens in a changeProperty request of
WM_HINTS. Could also be a ChangeWindowAttribute. Unfortunately, xmond's "block
request" feature doesn't work as expected, so it's hard to find out
experimentally which exact request "does" it. However: one thing is sure: there
are no GrabKeyboard, SetInputFocus, etc. requests. The only Grab* there is are
a couple of GrabServer calls, but these look benign (used more like a mutex, I
suspect). Xmon seems to have been unmaintained since before the 90's, do you
happen to know another X protocol debugger which is more recent and better
maintained? Thanks

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
kwin mailing list
kwin@kde.org
https://mail.kde.org/mailman/listinfo/kwin
[prev in list] [next in list] [prev in thread] [next in thread]