Bug 244625 - KWin behaves oddly with WM_HINTS.input == false
Summary: KWin behaves oddly with WM_HINTS.input == false
Status: RESOLVED DUPLICATE of bug 234926
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: git master
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-14 18:24 UTC by Alex Merry
Modified: 2010-07-14 19:03 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Test case (1.87 KB, application/x-gzip)
2010-07-14 18:24 UTC, Alex Merry
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Merry 2010-07-14 18:24:43 UTC
Created attachment 49147 [details]
Test case

Version:           SVN (using Devel) 
OS:                Linux

I'm not sure whether this is incorrect behaviour on KWin's part or not, but it is annoying (see http://code.google.com/p/cellwriter/issues/detail?id=34).

When an application sets the input flag of WM_HINTS to false (preventing the window manager from passing focus to it), pressing a mouse button down on the window when running under KWin sends an XLeaveWindowEvent to the window.  On other window managers this doesn't happen (the ButtonPress event gets sent, but not the LeaveWindow/Crossing event).

Reproducible: Always




Attached is are two test cases, one in GTK+ and one in Qt.  Run make to build them, and then run ./gtk-test or ./qt-test to run one or the other.

The apps basically just set the input hint to false and print out logs of LeaveWindow events.  The GTK+ one also prints out button press events (you can see that the LeaveWindow event happens before the ButtonPress event).
Comment 1 Alex Merry 2010-07-14 18:26:40 UTC
I should point out that the other window managers I've tried are Metacity and whatever XFCE4 uses.  I tested all three in an XFCE4 environment, to make sure that it was just the window manager.
Comment 2 Thomas Lübking 2010-07-14 19:03:04 UTC

*** This bug has been marked as a duplicate of bug 234926 ***