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).

That seems problematic. We need to write spec's based on the reality, not desires of various people involved in writing them. We should probably remove all those types not planned to be supported by Blink/Gecko/WebKit.

> 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.

Yeah, we should probably do that.

FWIW, I believe WebKit supports `text/plain`, `text/html`, `text/uri-list`, and `image/png` but certain native formats like web archive, tiff, etc... are transformed as text/html, image/png in our end.

@whsieh

-- 
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-843539363