After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 89179 - no way of ignoring Notify(Un)Grab FocusChange events
no way of ignoring Notify(Un)Grab FocusChange events
Status: VERIFIED INCOMPLETE
Product: gtk+
Classification: Platform
Component: Backend: X11
2.0.x
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: 89180
 
 
Reported: 2002-07-26 23:27 UTC by Mark McLoughlin
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.0


Description Mark McLoughlin 2002-07-26 23:27:44 UTC 
gdk should either ignore FocusChange events with xfocus.mode == NotifyGrab
|| xfocus.mode == NotifyUngrab or allow applications to differentiate
between FocusChange events generated by grabs and normal focus change events.

In gdk_event_translate we have 

          /* gdk_keyboard_grab() causes following events. These events confuse
           * the XIM focus, so ignore them.
           */
          if (xevent->xfocus.mode == NotifyGrab ||
              xevent->xfocus.mode == NotifyUngrab)
            break;

but its disabled.

I'll be assigning a panel bug as a dependancy on this for details of why
this would be useful
Comment 1 Owen Taylor 2002-07-29 20:23:29 UTC 
Are you sure bug 89180 isn't really a metacity bug?

GTK+ should only ever think a window has focus when it is
actually getting keyboard events.
Comment 2 Owen Taylor 2002-07-30 03:00:52 UTC 
I guess I need more information to really understand this
request ... I don't think it's generally right for apps
to do stuff on focus out that doesn't get undone on
focus in, otherwise.

Please reopen if you add more comments.
Comment 3 Kjartan Maraas 2003-10-29 12:34:48 UTC 
Mark, has all information Owen asked for been given?
Comment 4 Mark McLoughlin 2003-12-10 16:05:17 UTC 
Okay, the details behind all this are totally lost on me know
and the behaviour of Metacity seems to have changed such
that I can't reproduce the original problem so closing the bug ...