[w3ctag/design-reviews] ClipboardChange event API (Issue #1017)

こんにちは TAG-さん!

I'm requesting an early TAG design review of ClipboardChange event API.

The clipboardchange event is fired 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¹: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/ClipboardAPI/clipboard-change-event-explainer.md
  - Specification: https://www.w3.org/TR/clipboard-apis/#clipboard-event-clipboardchange
  - User research: Web based spreadsheet apps like Excel Online and web based remote desktop client apps have shown interest in this API. Please refer to the explainer document for further details about their use cases.
  - Security and Privacy self-review²: https://docs.google.com/document/d/1CjIORGpRK776O0YNF7Ah2FtQpA0ziNz20sFy-wWAzPE/edit?tab=t.0#heading=h.xzptrog8pyxf
  - Primary contacts:
   - Rohan Raja (@roraja), Microsoft
   - Rakesh Goulikar (@ragoulik), Microsoft
  - Organization/project driving the specification: Microsoft
  - Multi-stakeholder support³:
 - Chromium comments: https://issues.chromium.org/issues/41442253
 - Mozilla comments: https://github.com/mozilla/standards-positions/issues/NNN
 - WebKit comments: https://github.com/WebKit/standards-positions/issues/NNN
 -  https://github.com/WICG/proposals/issues/186

Further details:

  - [x] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/design-principles/) ✅ 2024-11-21
  - Relevant time constraints or deadlines: Jan, 2025
  - The group where the work on this specification is currently being done: Microsoft
  - The group where standardization of this work is intended to be done (if different from the current group): Microsoft
  - Major unresolved issues with or opposition to this specification:
  - This work is being funded by: Microsoft

You should also know that...

The [design doc]( https://docs.google.com/document/d/1bY2pzV6PSX56fiFcrXEgOjpFen07xaxmnsM5dqXFE1U/edit#heading=h.lem8rnjx4cw8) of this feature for Chromium might be useful for review. Code changes for a prototype implementation can be found [here](https://chromium-review.googlesource.com/c/chromium/src/+/5832111).

------------------------------------------------------------------------------------
CAREFULLY READ AND DELETE CONTENT BELOW THIS LINE BEFORE SUBMITTING

Use links to content rather than pasting text into this issue. Issues are ephemeral and most of the material we are asking for has long term value.

Please preview the issue and check that the links work before submitting. Please make sure anyone with the link can access the document. We may refuse to review anything that is not public.

¹ An explainer must address user needs and contain examples of use. See our [explanation of how to write a good explainer](https://tag.w3.org/explainers/).

² Even for early-stage ideas, a Security and Privacy questionnaire helps us understand potential security and privacy issues and mitigations for your design, and can save us asking redundant questions. See https://www.w3.org/TR/security-privacy-questionnaire/.

³ For your own organization, you can simply state the organization's position instead of linking to it.  This includes items on [Mozilla standards-positions](https://github.com/mozilla/standards-positions), and [WebKit standards-positions](https://github.com/WebKit/standards-positions).  Chromium doesn't have a standards-positions repository and [prefers](https://source.chromium.org/chromium/chromium/src/+/main:docs/standards/positions/GoogleChrome/README.md) to use comments from the teams that maintain the relevant area of their codebase.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1017
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1017@github.com>