- From: Dan Clark <notifications@github.com>
- Date: Fri, 10 Jan 2025 17:03:11 -0800
- To: w3c/clipboard-apis <clipboard-apis@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/clipboard-apis/issues/232/2584972221@github.com>
Looping in @roraja and @ragoulik who had been working on `clipboardchange` event. Since this is basically solving the same problem as `clipboardchange`, I hope there's some opportunity to collaborate. I want to dial in on [this part](https://github.com/explainers-by-googlers/clipboard-contents-id?tab=readme-ov-file#functionality-itself): > There is another proposed API for tracking clipboard changes - a clipboardchange event. However, even if implemented and standardized, it operates differently. Instead of determining if a change has occurred between two points in time, it provides real-time notifications for every change, without detailed information about the cause. Therefore, if your app also writes to the clipboard, it can be challenging to determine whether you or another source caused the change (especially with multiple windows/tabs of the same app open), potentially leading to unnecessary data transfers or having to implement comparison anyway. In case of contentsID(), you can save the new token just after writing - and it will be irrelevant for all active tabs/windows irrelevant what caused the change, only that this change is already in sync with the remote and no action is needed. @roraja, @ragoulik, is this a problem that you encountered with `clipboardchange`? Is there information that could be added to the event to allow an app to determine whether a given clipboard change came from the app itself? If not, should we consider whether `clipboardchange` should be superseded by clipboard contents ID? I'm not sure if both `clipboardchange` and contents ID will be necessary; one might be enough. Lastly, I suspect that the privacy concerns [raised at TPAC](https://github.com/w3c/clipboard-apis/issues/227#issuecomment-2397150516) about `clipboardchange` will apply equally to clipboard contents ID. That would probably be the biggest barrier to work through to get something like this supported broadly. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/clipboard-apis/issues/232#issuecomment-2584972221 You are receiving this because you are subscribed to this thread. Message ID: <w3c/clipboard-apis/issues/232/2584972221@github.com>
Received on Saturday, 11 January 2025 01:03:15 UTC