Re: [w3c/permissions] Drop .request() (#83)

An argument for keeping something like `request()`:

One place where I would like to use `request()` is with the clipboard API.

(1)
We would like to have a Permission that protects receiving the `clipboardchange` event (since even though the event doesn't contain clipboard data, it might still reveal info about the user).

The obvious approach would be to use `request()` and once it is granted, then the events will start being sent.

(2)
We've also had a request for separate "read" and "write" permissions. But without an entry-point that allows requesting "full" access, there will be multiple independent permission checks that might lead to user interaction: once for reading, once for writing and a separate time for listening ("clipboardchange").


-- 
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/83#issuecomment-330362220