[Wayland-bugs] [Bug 748892] wayland: focus issue with gnome-terminal

[gtk+ (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=748892

--- Comment #13 from Carlos Garnacho <carlosg at gnome.org> ---
(In reply to Olivier Fourdan from comment #12)
> I doubt this is specific to GtkMenu tbh, maybe gdk-wayland backend.

Yeah, my suspicion involving GtkMenu also involved GDK getting it into a
confused state (eg. not sending GdkEventGrabBroken properly or somesuch)

> 
> It seems to me that the grabs get released when a "grab-notify" signal is
> emitted from  _gtk_widget_grab_notify() called by
> gtk_grab_notify()/gtk_grab_notify_foreach() in gtk/gtkmain.c 

I'm talking about GDK grabs, although those usually go hand in hand with GTK+
ones.

> 
> In the case of a GtkMenu with a window-group, that signal is not emitted for
> the GtkMenu because of the portion of code the patch removes when using
> Wayland (I do have a branch with tons of logs added that tend to show this,
> I can share the -ugly- patch and/or logs if needed)
> 
> I think we do not see this in x11 simply because the grab gets released
> automatically by the X server when the window menu is unmapped but Wayland
> has no grab per se (yet) so this is all managed by signals in gtk. 
> 
> Or am I mistaken?

Yes, right. X11 defines how do grabs interact, and the grab mechanism in GDK is
largely based on it (in order to cater for client-side windows). On other
backends we must emulate a similar behavior out of the platform specific
semantics.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-bugs/attachments/20150617/68f092f2/attachment.html>