- From: Dan Burzo <notifications@github.com>
- Date: Mon, 21 Aug 2017 02:15:03 -0700
- To: w3c/clipboard-apis <clipboard-apis@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 21 August 2017 09:15:43 UTC
As mentioned in the comments here: https://github.com/w3c/clipboard-apis/issues/9 there are separate security concerns with _reading_ and _writing_ data for custom MIME types. I'm reopening the discussion for the _reading_ part. It sounds like unmediated access to the clipboardData in all available formats may pose a privacy concern, so it may be best to require some sort of consent from the user (as the previous thread suggested). I don't feel confident enough to make a concrete proposal, but wanted to reiterate the realm of possibility enabled by such a feature in providing interop between web and the OS. ## Current browser status & related issues * Safari provides unmediated access to the clipboardData in all formats * Chrome team [is skeptical](https://bugs.chromium.org/p/chromium/issues/detail?id=487266#c5) in enabling custom MIME types * Firefox team [decided on WONTFIX](https://bugzilla.mozilla.org/show_bug.cgi?id=1389919) due to concerns raised on the Chromium thread -- 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/46
Received on Monday, 21 August 2017 09:15:43 UTC