- From: Gary Kacmarcik <notifications@github.com>
- Date: Thu, 28 Sep 2017 17:36:49 -0700
- To: w3c/permissions <permissions@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/permissions/issues/158/332999946@github.com>
@raymeskhoury With respect to item 4, how do you think that should work for clipboard? We have `navigator.clipboard`, so that people can call `clipboard.read()` and `clipboard.write()` and have the permissions checked just before the resource is accessed. These methods would request `read` and `write` clipboard access, respectively, as needed. But we also need a way to request `full` access[1], and since there is no clipboard API that requires `full` access, it would need to be done in some sort of `clipboard.request()` method. But I don't think it makes sense for this `clipboard.request` method to return a handle to a resource. Would it just return `navigator.clipboard`? Because returning a handle like this implies that the handle defines the scope of the access, which would not be true in this case. And if we remove `navigator.clipboard` and require that a clipboard handle be requested beforehand, then that undermines the model that @martinthomson discusses in #83. My preference is for there to be a `clipboard.request()`, but I don't think it makes sense for it to return a handle to the clipboard. [1] Note: `full` clipboard access would grant read/write clipboard access without requiring a user 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/permissions/issues/158#issuecomment-332999946
Received on Friday, 29 September 2017 00:37:10 UTC