Re: [w3c/clipboard-apis] Add Web Custom format (PR #175)

> Do we care about the interop across legacy clipboard API and async clipboard API for custom type?

The async clipboard API model is fairly different, so I'm not sure if we can interop with legacy types. The web custom types are stored inside a JSON map structure, with fixed number of native web clipboard formats, and a well-defined format structure that helps the native apps parse the content of the format. At least in Chromium, the parsing of the custom types requires browser specific pickle types to serialize and deserialize the content, so it's not possible to add support for this format to the new web custom format.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/clipboard-apis/pull/175#issuecomment-1142374996
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/clipboard-apis/pull/175/c1142374996@github.com>