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

The Web Editing Working Group just discussed `Sanitize clipboard issue`.

<details><summary>The full IRC log of that discussion</summary>
&lt;Travis> Topic: Sanitize clipboard issue<br>
&lt;Travis> github: https://github.com/w3c/clipboard-apis/issues/150<br>
&lt;Travis> BoCupp: what do we need from the WG on this issue?<br>
&lt;Travis> snianu: We will be taking this discussion to the chromium security group (for chromium only).<br>
&lt;Travis> BoCupp: pastes are unpredictable...<br>
&lt;Travis> .. can't tell if a 3rd party messes with the clipboard.<br>
&lt;Travis> .. the question is whether there's some expected  behavior from App to browser...<br>
&lt;Travis> whsieh: We were thinking about adding things to the spec to fix compatibility in the short term. But, if we keep this the same (left to user agent discretion), we are OK with that.<br>
&lt;Travis> BoCupp: We don't think that keeping the spec as-is will be harmful, etc. Propose we can close the issue now.<br>
&lt;Travis> ACTION: BoCupp to close this issue; keep whsieh appraised of the security review (as FYI).<br>
</details>


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