Contact emails ror...@microsoft.com<mailto:ror...@microsoft.com>, ragou...@microsoft.com<mailto:ragou...@microsoft.com>
Explainer https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/ClipboardAPI/clipboard-change-event-explainer.md Specification https://github.com/w3c/clipboard-apis/pull/239 Summary The "clipboardchange" event fires whenever the system clipboard contents are changed either by a web app or any other system application. This allows web-apps like remote desktop clients to keep their clipboards synchronized with the system clipboard. It provides an efficient alternative to polling the clipboard(using Javascript) for changes. Blink component Blink>DataTransfer<https://issues.chromium.org/issues?q=customfield1222907:%22Blink>DataTransfer%22> Search tags clipboard change event<https://chromestatus.com/features#tags:clipboard%20change%20event>, clipboardchange<https://chromestatus.com/features#tags:clipboardchange>, clipboard monitor<https://chromestatus.com/features#tags:clipboard%20monitor> TAG review https://github.com/w3ctag/design-reviews/issues/1017 TAG review status Issues addressed Origin Trial documentation link https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/ClipboardAPI/clipboard-change-event-explainer.md Risks Interoperability and Compatibility None Gecko: No signal (https://github.com/mozilla/standards-positions/issues/1115) WebKit: No signal (https://github.com/WebKit/standards-positions/issues/429) Web developers: Positive 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. Other signals: WebView application risks Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? None Goals for experimentation - Primary Objective: Validate the clipboardchange event API design and developer adoption patterns in real-world web applications before standardization. - Track clipboardchange event API developer engagement metrics and growth trajectories through the counters implemented. - API Ergonomics Validation: Test whether the event interface and focus requirements work intuitively for developers - Developer Adoption Patterns: Understand how developers integrate the API into existing workflows through the community feedback. Experiment risks None: - There are no data storage implications with this event. - This is a non-critical functionality since this is an enhancement and not a major dependency. All current clipboard workflows continue to function without the event. Ongoing technical constraints None Debuggability None Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)? Yes Is this feature fully tested by web-platform-tests<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>? Yes wpt.fyi/results/clipboard-apis/async-navigator-clipboard-change-event.tentative.https.html (Note - Some tests are failing on wpt.fyi infra due to flakiness which is being looked into, it runs fine in Chromium CQ runs. Test failures in Edge are probably due to the feature flag being disabled in the test environment) Flag name on about://flags None Finch feature name ClipboardChangeEvent Requires code in //chrome? False Tracking bug https://issues.chromium.org/issues/41442253 Estimated milestones Shipping on desktop 142 Origin trial desktop first 140 Origin trial desktop last 142 Shipping on Android 142 Origin trial Android first 140 Origin trial Android last 142 Origin trial WebView first 140 Origin trial WebView last 142 Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5085102657503232?gate=6192789839413248 Links to previous Intent discussions Intent to Prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/67454fad.2b0a0220.19a388.0284.GAE%40google.com This intent message was generated by Chrome Platform Status<https://chromestatus.com>. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/SEYP153MB1545744F60C0B50919C5AA6AC454A%40SEYP153MB1545.APCP153.PROD.OUTLOOK.COM.
