Re: [w3c/clipboard-apis] Clipboard Change Event API (Issue #227)

From TPAC 2024 minutes:

> [w3c/clipboard-apis#227](https://github.com/w3c/clipboard-apis/issues/227)
> Rohan: Discuss some proposed changes to the clipboardchange event
> What is this event? Fired whenever the clipboard is changed, inside or outside the browser
> This allows the app to respond to these changes
> We already have a basic spec.
> We'd like to talk about the proposed changes.
> 
> Usage scenario:
> (1) In remote access, synchronizing the clipboard between the local and remote machine.
> To make a seamless experience
> (2) rich web editors. in a WP you might have multiple case format options and want to show those options to the user. Only allow the available options. DIsable those options which are not available.
> 
> Olli: Wondering if it could ever be implemented in Firefox. What about other browsers?
> Megan: Not sure if Webkit would do it either.
> 
> Olli: Only implemented in Chrome, and they have a Permission.
> 
> Etienne: This could be done by polling, right?
> 
> Olli: Not on FF because it requires a user interaction to use.
> 
> Sanket: What mitigations could be in place to make you feel better about it.
> 
> Etienne: Your concerns are mostly privacy-related?
> 
> Olli: Also, with the current Permissions model in FF (and Safari?) this would not be safe to implement.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/clipboard-apis/issues/227#issuecomment-2397150516
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/clipboard-apis/issues/227/2397150516@github.com>