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

> > And we also still have a discussion going on over in #150 as to whether these sanitization options make sense. It's not clear to me how this is ready for evaluation (or shipping).
> 
> #150 is related to writing unsanitized HTML content under the standard HTML format, not the custom format that this feature is about. I think we should evaluate this separately as custom formats are unsanitized content by definition. Also we had this discussion in multiple meetings with Apple and Google folks, and we all agreed to add this feature to the spec in a non-normative note. Here are the meeting minutes: [w3c/editing#334 (comment)](https://github.com/w3c/editing/issues/334#issuecomment-933939592)

I don't see how? This PR adds `unsanitized` as a dictionary option to `ClipboardItem`. I see no reason that's necessarily if we don't add `unsanitized` in the first place.

-- 
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/clipboard-apis/pull/162#issuecomment-974298824