Re: [w3c/clipboard-apis] Clipboard Permission (#51)

@hallvors

Still under discussion, but our current thoughts are:
- Write access would require a user gesture (just like today) **unless** Read permission was already granted (because Read is stronger than Write).
- Read access would require a Permission

For a user-triggered paste (where the UA knows it's a paste), it should also be OK with a gesture, but note that this would not apply for apps that create their own custom "paste" button.

One thing we're not sure about is how much of that (the user gesture requirement) should be an explicit requirement in the spec, and how much should be left as optional for browsers. That depends in part on whether or not there's agreement. I've created a [separate bug](https://github.com/w3c/clipboard-apis/issues/52) to track this.

_Note: This behavior is probably more clear if we rename "allowRead" to be "fullAccess". So that the basic `{ clipboard }` permission controls write access to the clipboard and `{ clipboard fullAccess=true }` grants read and write without requiring a gesture._

-- 
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/51#issuecomment-328975923