Re: [w3c/clipboard-apis] Should clipboard-write permission be removed too? (Issue #163)

I'm updating the MDN Clipboard API docs to reflect the current state of play. The situation is confusing. Could I get confirmation/denial of the following:

- `read()`/`readText()`:
  - The consensus and spec intent is to gate reading on transient activation rather than using `clipboard-read` permission
  - The  `clipboard-read` permission has been removed from the permissions API.
  - The  `clipboard-read` permission has been partially removed from the Clipboard API but is still referred to in a few places.
  - FF and Safari gate on transient activation and don't use the permission.
  - Chrome gates on  `clipboard-read` and if it is granted does not require transient activation. (result from testing current Chrome)
- `write()`/`writeText()`:
  - The spec team intent is to gate writing on transient activation rather than using `clipboard-write` permission
  - The  `clipboard-write` permission has been removed from the permissions API but without consensus from Chrome.
  - The  `clipboard-write` permission is still in the Clipboard API
    - Spec mentions the permission has been removed
    - _this_ issue indicates an intent/desire to remove it and use transient activation
    - this issue indicates consensus not reached, and looks like is not being chased.
  - FF and Safari do not use write permissions and never will. 
  - Chrome gates on  `clipboard-write` and if it is granted does not require transient activation.

Given the removed permissions, I'm not sure what is expected by the spec/spec team.
Can you give me some kind of view on where the spec and browsers are heading? My current plan is to assume that transient activation for read/write is what is expected and document the read/write permissions as incompatible, but I'd rather be "right".

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/clipboard-apis/issues/163#issuecomment-1878072165
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/clipboard-apis/issues/163/1878072165@github.com>