https://bugs.kde.org/show_bug.cgi?id=464142
Pedro V <voidpointertonull+bugskde...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |voidpointertonull+bugskdeor
| |g...@gmail.com
--- Comment #1 from Pedro V <voidpointertonull+bugskde...@gmail.com> ---
I believe this needs more info as there's quite a bit of uncertainty in the
report, but overall it doesn't sound like a bug, more like a potential feature
request.
If the clipboard is synchronized between multiple hosts, then it doesn't seem
to be too surprising that copying on one host results in the clipboard change
getting propagated even over multiple hops. So given an A <-> B <-> C setup, A
<-> C synchronization isn't really a bug because technically it's either (A ->
B, B -> C) or (C -> B, B -> A) synchronization pairs, both being allowed.
If the assumption is right, then I could see this being turned into a feature
request of either:
- Splitting the clipboard sharing functionality to have separate send and
receive options with both being enabled for the current behavior, but the
directions could be separately toggled to break chains
- Adding explicit clipboard sending functionality for fine grained control, so
there would be no automatic propagation at all when that would be used
Technically these options are not mutually exclusive, and they would even
compliment each-other with some well needed extra security by a host
potentially being configured to ignore received clipboard data even when it's
manually pushed while still sending if/when desired.
--
You are receiving this mail because:
You are watching all bug changes.
