[Wayland-bugs] [Bug 757558] gtk_window_move() unreliable in Wayland?

[gtk+ (GNOME Bugzilla)]

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

Olivier Fourdan <ofourdan at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ofourdan at redhat.com

--- Comment #18 from Olivier Fourdan <ofourdan at redhat.com> ---
See also bug 759738 

Now (in gtk+ 3.20) the gdk backend will use a subsurface for popup windows when
possible, ie when a parent is specified, so we don't require a grab anymore.

But I reckon the given reproducer is broken:

1. it creates a e_emoticon_tool_button_new ();
2. The corresponding e_emoticon_tool_button_init() tries to get the toplevel
window from gtk_widget_get_toplevel (GTK_WIDGET (button));
3. But because the button si not yet added to the window,
gtk_widget_get_toplevel() will necessarily return the buttn itself, therefore
GTK_IS_WINDOW (toplevel) is always wrong and gtk_window_set_transient_for(0 is
never called.

Too bad, because it it was, I think it would work as-is with gtk+ 3.20.

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