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

@snianu and I discussed offline.  I don't see any of the points discussed since [this post](https://github.com/w3c/clipboard-apis/issues/150#issuecomment-1031684598) from @annevk as being a blocker for us.

Both of the points mentioned:

> * The same behavior for the new and legacy API.
> * Optional, implementation-defined modification of the contents to uphold user agent privacy requirements.

...allow for Apple's preferred same-origin behavior, as well as our preferred behavior for Chromium, which is to allow unsanitized access to well-known formats like `text/html`, which would be consistent with our current behavior for the legacy Clipboard Event API.

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

Message ID: <w3c/clipboard-apis/issues/150/1033465241@github.com>