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 770784 - Wayland: Looong popup windows from combobox misplaced
Wayland: Looong popup windows from combobox misplaced
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: Wayland
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
https://gitlab.gnome.org/GNOME/mutter...
Depends on:
Blocks:
 
 
Reported: 2016-09-03 11:22 UTC by Timm Bäder
Modified: 2018-04-13 08:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot showing the problem (577.47 KB, image/png)
2016-09-06 11:49 UTC, Timm Bäder
Details

Description Timm Bäder 2016-09-03 11:22:02 UTC
Simple to reproduce:
 - Open tests/testcombo
 - Click on the Looong combobox (the one at the bottom)

If I move the window so that combobox is at the bottom edge of the screen, the menu appears at the top of the screen, if I move the window further up, I can't see the menu at all (I assume it's somewhere off screen).
Comment 1 Matthias Clasen 2016-09-06 11:02:22 UTC
Can you take some screenshots ? I don't reproduce this here
Comment 2 Timm Bäder 2016-09-06 11:49:47 UTC
Created attachment 334896 [details]
Screenshot showing the problem

This is a screenshot, my screen is 1080px high. Now that I look at it again, this might also be a mutter bug but I can't test in older mutter because of the xdg-shell version conflict.
Comment 3 Matthias Clasen 2018-02-10 04:58:04 UTC
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 4 Daniel Boles 2018-04-13 08:33:14 UTC
still an issue but more on the Mutter side:
https://gitlab.gnome.org/GNOME/mutter/issues/105
Comment 5 Jonas Ådahl 2018-04-13 08:52:39 UTC
Should we really close this bug? It's first and foremost a gtk+ issue, and should hopefully be fixed in gtk+, if not in gtk+-3 then at least in gtk+-4. The only thing mutter can do is to mitigate the invalid values gtk+ sends.
Comment 6 Daniel Boles 2018-04-13 08:55:22 UTC
I based that on what Olivier said at the Mutter bug before moving it from GTK+:

>>>
On further consideration, I am convinced this is not a bug in gtk+ nor gdk Wayland backend.

The X11 implemtatnation needs to know the global offset, clamping the values in gtkmenu will break that.

Wayland backend could do the clamping, but that obviously breaks any chance oof having the right position, ever (as we would pass wrong values to the Wayland compositor).

So the only ral solution to this problem is to fix the Wayland compositor, ie mutter.
>>>

I was deferring to one expert, but if another disagrees, please reopen indeed. :)