[Wayland-bugs] [Bug 774148] New: Gtk.Popover misplacement in Wayland (conflict between set_relative_to() and set_pointing_to()
gtk+ (GNOME Bugzilla)
bugzilla at gnome.org
Wed Nov 9 15:14:11 UTC 2016
https://bugzilla.gnome.org/show_bug.cgi?id=774148
Bug ID: 774148
Summary: Gtk.Popover misplacement in Wayland (conflict between
set_relative_to() and set_pointing_to()
Classification: Platform
Product: gtk+
Version: 3.20.x
OS: Windows
Status: NEW
Severity: normal
Priority: Normal
Component: Backend: Wayland
Assignee: gtk-bugs at gtk.org
Reporter: cedric.bellegarde at adishatz.org
QA Contact: gtk-bugs at gtk.org
CC: rob at robster.org.uk, wayland-bugs at lists.freedesktop.org
GNOME version: ---
Created attachment 339399
--> https://bugzilla.gnome.org/attachment.cgi?id=339399&action=edit
test.py
Description of problem:
When having a Gtk.Popover relative to a Gtk.Popover child, widget is misplaced
in Wayland (no issue with Xorg).
How reproducible:
Run test.py (attachement) like this:
python3 test.py
Steps to Reproduce:
1. Click on "Click me" button
2. Click on "Click me again" button
Actual results:
Popover is misplaced
Expected results:
Popover placed at set_pointing_to() of set_relative_to() widget
Additional info:
GDK_BACKEND=x11 python3 test.py fix the issue
--
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/20161109/aea7ec7b/attachment.html>
More information about the wayland-bugs
mailing list