The current version of wl_data_device.selection (i.e. copy-paste offers) requires keyboard focus. In effect, this makes it a requirement to have a keyboard attached in order to copy paste. This is not a reasonable requirement, especially since various types of hardware that may want to run a Wayland compositor with copy-paste capabilities may not have nor be able to have, a keyboard. This needs to be fixed, probably by extending wl_data_device.selection with a focus like event. For backward compatibility, we probably need to make this focus like event equivalent to keyboard focus for when the seat has the keyboard capability; but it needs to be sent regardless whether it has or not.
I see this is a pretty old bug. I'm not sure how this focus thing is related to copy/pasting in general but copy/paste issues is what still stops me from using wayland. I want to just link to a few issues related to copy pasting: https://bugzilla.redhat.com/show_bug.cgi?id=1410912 https://github.com/SirCmpwn/sway/issues/1012 https://github.com/gnunn1/tilix/issues/893 Basically there are a lot of questions around handling a primary selection buffer and handling copy/paste between x11 and wayland native apps. Also I'm very much concerned about clipboard manager support as I think it is extremely useful for people copy pasting multiple things and switching between copied strings. I'm sorry if this is not related to the described issue here. If so, what would be a good place to discuss the overall copy/paste experience of wayland?
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/wayland/wayland/issues/37.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.