- From: Luke (Zgroza) Klimek <notifications@github.com>
- Date: Tue, 07 Jan 2025 10:03:04 -0800
- To: w3c/clipboard-apis <clipboard-apis@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/clipboard-apis/issues/232@github.com>
Hi, I’d like to propose an addition to the Clipboard API \- a way to efficiently check whether the clipboard has changed between two points in time without actually reading it. The primary use case that I have in mind would be to optimize the remote desktop solutions’ heuristics for local clipboard change detection. Another potential use case could be within the web versions of office-like applications, as they usually integrate context menus with information on what currently exists in the clipboard \- the exact interest of their developers in this however remains to be determined. You can find a more detailed explainer at [https://github.com/explainers-by-googlers/clipboard-contents-id](https://github.com/explainers-by-googlers/clipboard-contents-id). Could we schedule a discussion at an upcoming meeting to figure out: 1. Is there consensus to address this problem? 2. If not, what extra data could help show that the use case is important? 3. If the use case does have consensus: 1\. Can we check the explainer into [https://github.com/w3c/clipboard-apis](https://github.com/w3c/clipboard-apis)? 2\. What concerns do people have about the proposed API shape? 3\. How should this interact with the proposed `clipboardchange` event? -- Reply to this email directly or view it on GitHub: https://github.com/w3c/clipboard-apis/issues/232 You are receiving this because you are subscribed to this thread. Message ID: <w3c/clipboard-apis/issues/232@github.com>
Received on Tuesday, 7 January 2025 18:03:08 UTC