Re: [w3c/clipboard-apis] Add Custom Clipboard format support to async clipboard. (PR #162)

@annevk I think the main point of contention was the `unsanitized` option which we would like to keep since we want to support sharing of the custom format content across origins(e.g. from Excel online to PPT to Word online to Outlook etc) and able to write unsanitized HTML using the standard HTML format. For Safari it is moot because they don't want to support that scenario. In [our meetings ](https://github.com/w3c/editing/issues/334#issuecomment-933939592) with Apple folks, they raised the concern that a web spec shouldn't define platform specific clipboard format naming convention/format structure -- They wanted the OS to specify the custom formats. We think that these custom formats are special as they are generated by the web browsers, and the OS (have only checked Windows, CrOS, Android, Linux and Mac) already has support for custom formats, so standardizing at least the [custom format map](https://github.com/w3c/editing/blob/gh-pages/docs/clipboard-pickling/explainer.md#os-interaction-format-naming) shouldn't be an issue. I wouldn't say that they were completely opposed to the custom format concept in general (and neither are you :)) but if we don't want to standardize the [custom format map](https://github.com/w3c/editing/blob/gh-pages/docs/clipboard-pickling/explainer.md#os-interaction-format-naming) and `unsanitized` option, then I'm not sure what changes need to be made in the spec?

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

Message ID: <w3c/clipboard-apis/pull/162/c1006764036@github.com>