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

We are looking to implement the Clipboard Change Event API and spec for clipboardchange event exists today, [link](https://www.w3.org/TR/clipboard-apis/#clipboard-event-clipboardchange)
However, important details are missing and there is a need for calling out details explicitly to ensure spec is not open to interpretation.

Logging this issue to introduce the Clipboard change event API and call out the issues that need to be addressed.

**Description:**
The clipboardchange event fires whenever the system clipboard contents are changed. This allows web-apps like remote desktop clients to be notified and respond to changes to the system clipboard. It provides an efficient alternative to polling the clipboard for changes. 

**Explainer**:[ Clipboard change event explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/ClipboardAPI/clipboard-change-event-explainer.md)

Issues that needs to be addressed:

1. [Callout clipboadData (DataTransfer object) would be null in clipboardChange event object](https://github.com/w3c/clipboard-apis/issues/223)
2. [Callout clipboard-read permission is required to listen to clipboardchange](https://github.com/w3c/clipboard-apis/issues/224)
3. [Callout transient user activation should be applied for focus requirement.](https://github.com/w3c/clipboard-apis/issues/225)
4. [Callout details for cross-origin iframes and fencedframes](https://github.com/w3c/clipboard-apis/issues/226)

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

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