<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - GdkSelection does not support arbitrary named clipboards/selections on wayland" href="https://bugzilla.gnome.org/show_bug.cgi?id=770333#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - GdkSelection does not support arbitrary named clipboards/selections on wayland" href="https://bugzilla.gnome.org/show_bug.cgi?id=770333">bug 770333</a> from <a href="page.cgi?id=describeuser.html&login=thomas%40tommie-lie.de" title="Thomas Liebetraut <thomas@tommie-lie.de>"> Thomas Liebetraut</a> <pre>When I analyzed file-roller for the bug, I did not really understand why it has its own clipboard. I thought it was for drag-and-drop to/from other file-roller instances, but that works fine even on Wayland with the older version of Gtk+. I did not really focus on finding out *why* file-roller uses the clipboard, though. Eliminating dead code in file-roller (if it really is not necessary) is definitely a good idea. But this is still a bug either in Gtk+'s API documentation (which explicitly states that custom clipboards can be created this way) or the Wayland backend implementation (if Gtk+ developers think that custom clipboards are a feature worthwhile having).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>