[Wayland-bugs] [Bug 768177] CLIPBOARD target request after PRIMARY request times out. GDK_SELECTION_NOTIFY has wrong selection id

[gtk+ (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=768177

--- Comment #2 from Carlos Garnacho <carlosg at gnome.org> ---
Created attachment 330600
  --> https://bugzilla.gnome.org/attachment.cgi?id=330600&action=edit
wayland: Separate selection buffers and other per-selection atom data

This has most notably impact in selection buffers, because those were
shared across all selection atoms. This turned out wrong on 2 situations:
- Because the selection atom was set at SelectionBuffer creation time, the
  GDK_SELECTION_NOTIFY events generated will have unexpected info if the
  buffer is attempted to be reused for another selection.
- Anytime different selections imply different stored content for the same
  target.

This is better separated into per-selection buffers, so it's not possible
to get collisions if a same target is used across different selections.

-- 
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/20160629/c69d5028/attachment.html>