Bug 54238 - owner-events is not honoured on passive button grabs
Summary: owner-events is not honoured on passive button grabs
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/Input/Core (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-30 02:24 UTC by Peter Hutterer
Modified: 2018-12-17 17:26 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Peter Hutterer 2012-08-30 02:24:34 UTC
A passive grab with owner-events false should report events only if selected by the event mask. the owner-events field is ignored when the event that caused the grab activation is sent to the client (code as of 1.13RC5 is in ActivatePassiveGrab).

Test case:
- window with ButtonPress event mask set
- passive grab on window with empty event mask
- a button press on the window

For owner-events true, we expect a ButtonPress event
For owner-events false, we do not expect a ButtonPress event

This is an old bug, reproduced on 1.13RC5, 1.10.6 (RHEL6.3 server) and the RHEL5 xorg-x11-server-Xorg-1.1.1-48.76.el5.

This may be protocol spec ambiguity. It is not clear if the button press event should always be delivered to a client, regardless of the grab event mask.
Comment 1 Bastien Dejean 2013-03-22 11:05:56 UTC
The bug is still there in X.Org 1.14.0!
Comment 2 Peter Hutterer 2013-03-26 05:05:45 UTC
Given that this bug has been there for so many years, changing this behaviour is likely to break clients.
Comment 3 GitLab Migration User 2018-12-17 17:26:05 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/563.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.