Repository: guacamole-website Updated Branches: refs/heads/asf-site 4b6407b6f -> 45181cc21
GUACAMOLE-559: Deploy update to FAQ describing support for async clipboard API. Project: http://git-wip-us.apache.org/repos/asf/guacamole-website/repo Commit: http://git-wip-us.apache.org/repos/asf/guacamole-website/commit/45181cc2 Tree: http://git-wip-us.apache.org/repos/asf/guacamole-website/tree/45181cc2 Diff: http://git-wip-us.apache.org/repos/asf/guacamole-website/diff/45181cc2 Branch: refs/heads/asf-site Commit: 45181cc21a87acdd714db039f9b1992ac7e4b4af Parents: 4b6407b Author: Michael Jumper <mjum...@apache.org> Authored: Fri May 4 09:27:56 2018 -0700 Committer: Michael Jumper <mjum...@apache.org> Committed: Fri May 4 09:27:56 2018 -0700 ---------------------------------------------------------------------- content/faq/index.html | 26 ++++++++++++++++---------- 1 file changed, 16 insertions(+), 10 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/guacamole-website/blob/45181cc2/content/faq/index.html ---------------------------------------------------------------------- diff --git a/content/faq/index.html b/content/faq/index.html index 685a495..c9653e1 100644 --- a/content/faq/index.html +++ b/content/faq/index.html @@ -559,16 +559,22 @@ the âxrandrâ utility.</p> <h3 id="local-clipboard">Why donât you just use the clipboard directly instead of the box in the menu?</h3> <p>Guacamole actually already attempts to do this leveraging the <a href="https://www.w3.org/TR/clipboard-apis/">Clipboard -API</a> defined by the W3C. Browsers only -provide access to the clipboard under very strict circumstances, so these -attempts will fail unless the browser itself provides some means of explicitly -granting clipboard access.</p> - -<p>IE10 and IE11 will both prompt the user to grant clipboard access, and there is -a <a href="https://chrome.google.com/webstore/detail/clipboard-permission-mana/ipbhneeanpgkaleihlknhjiaamobkceh">third-party extension for -Chrome</a> -which provides similar functionality. Until a generic mechanism for granting -clipboard access exists across all browsers, these are really the only options.</p> +API</a> defined by the W3C, with support +for the asynchronous version of this API added via +<a href="https://issues.apache.org/jira/browse/GUACAMOLE-559">GUACAMOLE-559</a>. Browsers +vary in their level of support for this API, and some only provide access to +the clipboard under very strict circumstances.</p> + +<p>The following browsers are known to support clipboard access:</p> + +<ul> + <li>Google Chrome version 66 and later (via the <a href="https://www.w3.org/TR/clipboard-apis/#async-clipboard-api">Asynchronous Clipboard API</a>)</li> + <li>Older versions of Google Chrome using the third-party <a href="https://chrome.google.com/webstore/detail/clipboard-permission-mana/ipbhneeanpgkaleihlknhjiaamobkceh">Clipboard Permission Manager extension</a></li> + <li>IE10 and IE11 (via the older, synchronous version of the API)</li> +</ul> + +<p>This can be expected to change as the asynchronous version of the clipboard API +gains wider adoption.</p> <h3 id="copy-paste-events">I see the browser has âcopyâ and âpasteâ events. Why donât you handle these events so clipboard works?</h3>