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

List:       kde-bugs-dist
Subject:    [Bug 187718] Focus screwed up after closing emacsclient window (with
From:       Alain Knaff <kde () kde ! lka ! org ! lu>
Date:       2010-06-02 13:26:28
Message-ID: 20100602132628.31C2B4348B () immanuel ! kde ! org
[Download RAW message or body]

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





--- Comment #5 from Alain Knaff <kde kde lka org lu>  2010-06-02 15:26:23 ---
> the WM tool call is applied regardless of any focus protection level.

But then how come we have this problem at all? Why isn't focus protection level
"Extreme" then by default, if WM tool calls are applied regardless? Earlier in
this discussion, you said that there was no reliable/acceptable way how the WM
could tell its tools apart from other applications, so now which is it?

Also, the weird thing is that although the pager and the taskbar widgets work
despite "extrem" focus protection level (good), the "window list" widget *does*
get impacted. Or are there even several levels of "WM tool call", some of which
are affected by focus protection level, and some which aren't?

> i just tried "focus under mouse" and w/o protection the desktop is actually
> changed on mapping (any) window immediately. so there's no protection in this
> regard.
> i guess changing desktops is a kwin bug in this context

Indeed... except for the case of emacsclient, which seems to do it also with
"focus strictly under mouse". But emacsclient is doing weird stuff... on my
kubuntu box at home, it is actually warping the mouse pointer to a different
spot to get focus that way!

> mozillas aggressive
> focus pulling on low protection and click-to-focus is another beast. (it's
> likely switching the VD explicitly before calling focus)

Any idea how to spot this easily in xmon?

> this got a little messed up (i wasn't aware of your focus model in the
> beginning and the mozilla bug is known, sorry)

Good to know it's known, hopefully it will get fixed.

> input grabs are unrelated. this just means a client will receive input events
> exclusively

Ok, I'm not so familiar with all the different X calls, so I'd appreciate a
couple of hints what to look for... And isn't "focus" basically a fancy way of
saying that a client will receive all input events of type "keyboard"?

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]