On Wed, Jan 8, 2025 at 12:57 PM 'Luke Klimek' via blink-dev < blink-dev@chromium.org> wrote:
> Contact emails > > zgr...@google.com > > 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 > > Blink>DataTransfer > <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EDataTransfer%22> > Does any team own this component? A couple of years ago it was a black hole for bugs because it was not triaged. I'd be happy to learn that's no longer the case, otherwise I'm concerned about adding any additional functionality in this area without clear ownership. > Motivation > > 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. > > > Initial public proposal > > https://github.com/w3c/clipboard-apis/issues/232 > > TAG review > > None > > TAG review status > > Pending > > Risks > > Interoperability and Compatibility > > None > > > Gecko: No signal > > WebKit: No signal > > Web developers: No signals > > 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 > > > Debuggability > > None > > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ? > > No > > Flag name on about://flags > > None > > Finch feature name > > None > > Non-finch justification > > None > > Requires code in //chrome? > > False > > Estimated milestones > > No milestones specified > > > Link to entry on the Chrome Platform Status > > https://chromestatus.com/feature/5124993439236096?gate=5118994141675520 > > 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/CAG7s_oG8bwAa%2BRLx8MY_%2Bhcn1riUrMpzE%3DmZibRh%2BKNNtR7LWg%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAG7s_oG8bwAa%2BRLx8MY_%2Bhcn1riUrMpzE%3DmZibRh%2BKNNtR7LWg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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/CAGsbWzRf3k6UzXq-TfjiaSt2RdsKmn7JF8%3D5RWJG5s%2B5hZAsbQ%40mail.gmail.com.
