[
https://issues.apache.org/jira/browse/GUACAMOLE-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15785860#comment-15785860
]
Michael Jumper commented on GUACAMOLE-150:
------------------------------------------
Thanks for reporting this, however this is a bug - that functionality is simply
not implemented, even though the framework for supporting this exists at both
the protocol and API levels.
There was an initial attempt to get client-side support for non-test data
working (in this case, images specifically) via GUACAMOLE-55
([GUAC-1547|https://glyptodon.org/jira/browse/GUAC-1547]), but that was
partially reverted for the sake of release stability (GUACAMOLE-82).
The original issue, GUACAMOLE-55, was re-opened and development on that will
resume. There are, however, complicated browser-specific quirks which make this
non-trivial.
> onclipboard event doesn't fire on non-text clipboard data
> ---------------------------------------------------------
>
> Key: GUACAMOLE-150
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-150
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-client
> Environment: Linux Mint 18 64 bit
> Tomcat 8
> RDP access to Win2012 server
> Reporter: Marko Nikolić
>
> When clipboard data is selected in remote client, the event onclipboard
> should fire in {{Guacamole.Client}} object. However, this does not happen for
> non-text clipboard data.
> Previous versions explicitly supported only text in the clipboard. Starting
> from 0.9.10 version there is a code in {{app/client/types/ManagedClient.js}}
> , function {{onclipboard}}, that handles both textual and binary data.
> However, it still works only for textual data.
> The change is introduced by commit 8c54461 , but it seems that binary
> clipboard data isn't introduced in the server code also. The guacd reports
> the following when non-textual data is selected:
> guacd\[779\]: INFO: Ignoring unsupported clipboard data
> This looks misleading to me, as it gives the wrong impression that
> functionality exists. I believe it should be aligned, either by finishing
> implementation in server or removing non-functional implementation from
> client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
