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

I don't think changing the list of non-pickled mime types after we start with pickling would break anything (or at least I think we can design the pickling API to make sure of that). This is one reason why currently the explainer mentions that if a website specified that a particular mime type should be pickled, we'd still also write the unpickled version of the same type, if the type is supported that way. The pickled format won't undergo sanitization, while the unpickled one will. As such there is value in including both on the system clipboard.

Having said that, I do agree that it we should document what types are supported without pickling across browsers. In chrome that list currently is indeed also `text/plain`, `text/html` and `image/png`, although we're hoping/planning to add `image/svg+xml` to that list shortly.

I also agree we should invest more in making the async clipboard API spec more precise, for example I don't think it currently specified at all what should happen when a type isn't supported by the async clipboard API. Hopefully as part of the work on pickling we can make sure that all this gets better specified. We definitely should have done better here.

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