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

So part of the problem here that became more clear to me during a meeting is that some browsers have different behaviors for the "legacy" and "new" clipboard APIs. In particular the former does not sanitize and the latter does. It's not clear to me we want to enshrine that difference. Either we should sanitize consistently or not at all. (I could sanitization differing based on the origin (although that's not a fleshed out concept in the specification today), but not based on the API in use. Especially as the APIs do not have names that suggest these semantics.)

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