- From: Thomas Steiner <notifications@github.com>
- Date: Mon, 17 Jun 2024 05:10:51 -0700
- To: w3c/clipboard-apis <clipboard-apis@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 17 June 2024 12:10:55 UTC
I love the user case. This is more of a browser support request than a spec issue, though. For Chrome, the Async Clipboard API is being worked on in the context of Project Fugu 🐡. You can [request new Fugu features](https://bit.ly/new-fugu-request) through our bug tracker. For orientation, this is a [similar feature request](https://issues.chromium.org/issues/40808084) where support for a new image format is requested. If you [send me](mailto:tomac@google.com) the bug URL, I'm happy to help triage it. It's pretty much the same flow for the other browsers as well. (In Chromium-based browsers, there's [web custom formats](https://developer.chrome.com/blog/web-custom-formats-for-the-async-clipboard-api/) that allow you to copy anything, but it depends on support for the web custom format on the receiving end, that is, Abelton and friends.) -- Reply to this email directly or view it on GitHub: https://github.com/w3c/clipboard-apis/issues/218#issuecomment-2173232227 You are receiving this because you are subscribed to this thread. Message ID: <w3c/clipboard-apis/issues/218/2173232227@github.com>
Received on Monday, 17 June 2024 12:10:55 UTC