https://github.com/explainers-by-googlers/clipboard-contents-id
None
An API exposing a unique identifier of the current system clipboard contents. It is a supplement to the current Async Clipboard API and enables websites leveraging clipboard access to detect clipboard content changes much more efficiently.
The only somewhat reliable way to monitor clipboard changes is polling it at regular intervals - which is usually not efficient, especially in case of big contents' size.
There already exists a proposal that aims to make this better - clipboardchange event - but the functionality there makes it difficult to differentiate changes done externally from those originating from the app itself, as is the common occurrence in the Virtual Desktop Infrastructure clients. Leveraging any one - and preferably both of those APIs - would make current heuristics for clipboard monitoring much better.
We'll be working with the Web Editing Working Group and the clipboardchange event proponents to ensure the full system is coherent.
https://github.com/w3c/clipboard-apis/issues/232
None
Pending
None
Gecko: No signal
WebKit: No signal
Web developers: No signals
Other signals:
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
None
No
None
None
None
False
No milestones specified
https://chromestatus.com/feature/5124993439236096?gate=5118994141675520
This intent message was generated by Chrome Platform Status.
Contact emails
Explainer
https://github.com/explainers-by-googlers/clipboard-contents-id
Specification
None
Summary
An API exposing a unique identifier of the current system clipboard contents. It is a supplement to the current Async Clipboard API and enables websites leveraging clipboard access to detect clipboard content changes much more efficiently.
Blink component
--
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+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAG7s_oG8bwAa%2BRLx8MY_%2Bhcn1riUrMpzE%3DmZibRh%2BKNNtR7LWg%40mail.gmail.com.