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

Yeah. My understanding is that _if_ we want to explicitly define supported MIME types at all, we should just define the set of MIME types that Blink, Gecko, and WebKit already support.

From what I understand, this only includes `text/plain`, `text/html` and `image/png`. (It wasn't clear to me whether Firefox supports `text/uri-list` — I tried copying a URL from Safari and pasting into Firefox, but only observed `text/plain`).

Hypothetically, if we were to add to this set in the future, it seems that doing so should require both (1) implementation from all major browser engines, and (2) that it's possible to sanitize this data, if it has the potential to leak PII or otherwise trigger serious issues when pasted in native applications.

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