- From: Luke (Zgroza) Klimek <notifications@github.com>
- Date: Wed, 12 Mar 2025 04:27:04 -0700
- To: w3c/clipboard-apis <clipboard-apis@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 12 March 2025 11:27:08 UTC
zgroza left a comment (w3c/clipboard-apis#232) Thanks for your input, @ragoulik and @roraja\! Regarding your points: * I agree that having `clipboardchange` capabilities available would be beneficial for certain use cases. If `contentsId` is adopted, I would also support its integration into the `clipboardchange` API. * The flow proposed by @roraja seems valuable, especially because storing something like `contentsId` within the clipboard itself resolves potential race conditions arising from separate change-tracking and clipboard-reading mechanisms. While there are downsides, mostly related to the overhead of reading the clipboard and potentially triggering delayed rendering, the trade-off seems worthwhile from a VDI perspective. Therefore, if `clipboardchange` is adopted, there's less need for `contentsId` unless some new significant use cases come up. I'm leaving the Agenda+ label so we can discuss this during the upcoming Editing WG monthly call. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/clipboard-apis/issues/232#issuecomment-2717555623 You are receiving this because you are subscribed to this thread. Message ID: <w3c/clipboard-apis/issues/232/2717555623@github.com>
Received on Wednesday, 12 March 2025 11:27:08 UTC