Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150)

Per the [log of the last Web Editing WG meeting](https://github.com/w3c/clipboard-apis/issues/150#issuecomment-991151987) above, we agreed to leave the details of sanitization up to the UA, i.e. we won't attempt to standardize it at this time.  Additionally, to leave room for Safari to implement cross-origin restrictions or whatever policy they would like to use to govern access to the pickled formats (which are also unsanitized) @snianu will [land the PR for clipboard pickling](https://github.com/w3c/clipboard-apis/pull/162) without mentioning the `usanitized` option for `ClipboardItem`s and remove any language that talks about when to sanitize or not or allow access to pickled data or not.  I think adding a note saying that those particular behaviors are UA specific would be a good addition in the spec.

We don't think this will affect the developer experience.  We do expect that depending on whatever sanitization level the UA chooses to apply will just change the fidelity of the markup available to a paste operation,  but developers don't need to write different code and do need to deal with any shape of markup from the clipboard already.

Closing this issue.  If you think there needs to be any further discussion please reactivate.  Thanks!

-- 
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/issues/150#issuecomment-994181053