Re: [w3c/clipboard-apis] Active malicious PasteJacking exploits in-the-wild affecting user security owing to lack of sufficient consideration to identified and other security concerns (#142)

Anyone copying from, say, Google Docs with a CANVAS-based rendering engine depends on these features. The use cases are plenty, and unless you have specific and useful suggestions to improving the "security consideration" prose in the spec, I recommend the current editors close this issue.

You may want to ask your favourite browser to implement a "disable clipboard API" setting or write a browser extension that stops websites from using it. I think both are excellent ideas for the cautious. However, arguing that the spec should simply drop widely requested and widely used functionality is, respectfully, wasted time.

-- 
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/142#issuecomment-846056770