Re: [w3c/permissions] Requesting permission shouldn't imply storing it. (#93)

I'd like to propose we change our states to cover temporary permission (which could be reused as return values in the *access algorithm* to infer temporal and/or one-time access):

    'prompt'
    'allowed temporarily'
    'allowed'
    'blocked temporarily'
    'blocked'

I.e. add two "temporarily" states, and rename the one-off-sounding "denied" to a more permanent "blocked".

This matches language in a new UX re-design [currently being discussed in Firefox](https://bugzil.la/1267607). There seems to be value in communicating temporary access to users, so aligning what sites see with this might simplify things.

The exact meaning of "temporary" might be up for discussion, or left up to browsers. For instance, for cameras, temporary access may end once the last obtained camera stream is stopped, at which point reported access reverts to `'prompt'`. Also, some browsers may decide to re-prompt for each new stream obtained even in this temporary state (but whenever used as a return value from an *access algorithm*, `'allowed temporarily'` would nonetheless be overloaded to mean that one-off access has been granted).

Similarly, browsers might look at `'blocked temporarily'` and/or other criteria to decide whether a particular site should be automatically turned away without prompting the user again within this session or some time period, whereas `'blocked'` should probably never be changeable from a site.

In any case, there seems to be some room for innovation and/or open areas for discussion here. Thoughts?

---
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/93#issuecomment-215431087