Re: [w3c/editing] Explicitly define supported MIME types in Async Clipboard Spec (#305)

I'm not sure about overall interoperability data, but I'm aware that at least some of these formats also aren't supported / planned to be supported by Chromium as well. My understanding is that the spec intends to provide recommendations for formats browsers should support (and hence may not reflect actual supported formats on each platform).

For Chromium, a quick search suggests that there is at least [some implemented/planned clipboard support](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/clipboard/clipboard_mime_types.cc) for text/plain, text/html, image/svg+html, text/uri-list, image/png, and application/octet-stream, and no support for all the other types (besides as the undocumented/unspecified pickled formats that Blink/Webkit both support). For async clipboard, I'm aware that Chromium currently supports text/plain, text/html, and image/png.

What MIME types do WebKit/Safari and Gecko/Firefox currently support on the general clipboard or async clipboard API? We can build this interoperability data here, if we can't find it elsewhere. I'm aware that Webkit/Safari's Async Clipboard API supports the same formats as Chromium, plus text/uri-list, per [this blog post](https://webkit.org/blog/10855/async-clipboard-api/#:~:text=clipboarditem%2C%20which%20represents%20a%20single%20item%20on%20the%20system%20clipboard%20that%20may%20have%20multiple%20representations.%20currently%2C%20when%20reading%20and%20writing%20data%2C%20webkit%20supports%20four%20mime%20type%20representations%3A%20%22text%2Fplain%22%2C%20%22text%2Fhtml%22%2C%20%22text%2Furi-list%22%2C%20and%20%22image%2Fpng%22.), but I'm not sure what formats are supported in the overall clipboard for Webkit/Safari, or overall for Firefox. (later, this information should likely also go in [the MDN article](https://developer.mozilla.org/en-US/docs/Web/API/Clipboard_API) or similar)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/305#issuecomment-843407776