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

> > 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.
> 
> We added `unsanitized` to `ClipboardItemOptions` as it is optional and we don't want to create yet another member to track the unsanitized list. We don't need the `unsanitized` list during `write()`, we only need it for `read()`. I guess we could also make the `unsanitized` member optional in the dictionary. That way we could reuse this type without breaking anything? Let me know what you think.. These will be added as a non-normative note to the spec so browsers may or may not support this type.

I don't see how that makes sense for a Web API. It means if someone writes code using Safari, it may not work in Chrome / Edge. Generally, we'd like to avoid that sort of thing if possible. My perspective on this PR is that we need to resolve [the issue ](https://github.com/w3c/clipboard-apis/issues/150) first.

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