GNOME Bugzilla – Bug 767283
[Wayland] "Add a Column" dialog: drag and drop broken on wayland
Last modified: 2016-08-12 10:14:35 UTC
This affects evolution running inside a Gnome+Wayland session or running inside Weston. Steps to reproduce: 1. open evolution ("Mail") 2. in the table in the middle, right-click into the header (columns) and press "Add a Column…" 3. drag a column where you want to place it What happens: Columns can be dragged (and are transparent, which is weird and probably not intended). There are no indicators for the table showing that the column would be placed inside the table header. The table doesn't accept ("receive") any column. What should happen: One should be able to drag and drop new columns anywhere in the table. There should be indicators for visual feedback showing where the column will be dropped. Affected versions: gtk3-3.20.6-1.fc24.x86_64 evolution-3.20.2-1.fc24.x86_64
Thanks for a bug report. I tested this also with the 3.18.x of the evolution and the gtk+ and this doesn't work there either, under Wayland. I do not understand what changed under Wayland that the drag&drop there doesn't work, but it does work under X11. The problem is that the Wayland adds its own target type "DELETE" into the list of targets, before the one provided by the evolution, which broke the logic. Created commit a1a048c in evo master (3.21.3+) Created commit 01104dc in evo gnome-3-20 (3.20.4+)
I just tested 3.20.4, but it still isn't fixed. Steps to reproduce: 1. open evolution ("Mail") 2. half-maximize window to right screen half 3. in the table in the middle of the mailer component, right-click into the header (columns) and press "Add a Column…" 4. drag a column where you want to place it What happens: Indicators for where the tab will be placed (red arrows) are placed on some weird position on the screen. They often appear outside (!) the evolution window. Sometimes they appear on the other screen half as if evolution thought it were half-maximized on the left, not on the right.
Hrm, I do not know where I was looking when testing the previous change, even the evolution console showed some runtime messages from gdk which explain why it doesn't work. Of course, it was supposed to be addressed at the same time as the previous change. I'm sorry about that. Created commit 453dcf7 in evo master (3.21.90+) Created commit 0c474f1 in evo gnome-3-20 (3.20.5+)
Fix confirmed. Thank you!