<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Autocompletion menu doesnt working properly" href="https://bugzilla.gnome.org/show_bug.cgi?id=751651#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Autocompletion menu doesnt working properly" href="https://bugzilla.gnome.org/show_bug.cgi?id=751651">bug 751651</a> from <a href="page.cgi?id=describeuser.html&login=jadahl%40gmail.com" title="Jonas Ådahl <jadahl@gmail.com>"> Jonas Ådahl</a> <pre>I investigated this a bit, and for what i can see, builder tries to map (via GtkSourceView) a GtkSourceCompletionInfo (which is a gdk window with the hint "COMBO"). Combo windows usually gets mapped, and should here as well, as "xdg_popup" on the protocol level, but fails to do so because the window is not made transient for another, meaning from GDK's point of view, it is a stand alone window with no connection to the editor. In other words, I think this needs to be fixed in builder by properly marking the combo window as a child window to the parent window, so that GDK can properly make that connection on the protocol level as well. Note that, on Wayland, this is required to allow positioning and stacknig order to work as they should. I also imagine we can do the same hack/work-around for guessing a likely transient window in a similar way we do with popup menus. Is that something we want to do in GTK+ for combo windows as well?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>