Re: [w3c/editing] clarifications for the pickling design proposal (Issue #393)

> That means that, as long as OSs don't try to rule it out and pickled formats exposed by the web browser remain in the clipboard (i.e. are not wiped out then apps (and other sites) have a chance to receive that content. Right?

This is only possible if the native apps add support for web custom format. The custom mime type would be in the web custom format map. The app needs to read the map to fetch the native web custom clipboard format corresponding to the mime type, and use that format to read the content from the clipboard. This is explained [here](https://github.com/w3c/editing/blob/gh-pages/docs/clipboard-pickling/explainer.md#os-interaction-format-naming).

> How can it be insured that this is not the case for pickled formats? Lobbying that the receiving implementation is in a position to inform the user about the security implications?

I don't think we as browser vendors can make OS decisions, but AFAIK Windows is not going to drop support for custom formats as that would cause serious regressions in many apps including Chromium/Firefox browsers that rely on this behavior. So, I guess we could do some level of "lobbying" to ensure that the custom formats stay as is on all supported Windows versions.

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

Message ID: <w3c/editing/issues/393/1176400256@github.com>