Re: [permissions] Faking permissions (#54)

>Yes but presenting yet another complicated option to an user they likely don't understand, is really terrible solution.

I think the browser devs should ask a user first if he wants 3 or more options or just 2.

>Since permission is always asked just-in-time, we can make it so that app cannot tell difference between denial and operational error. For example, asking a geolocation and getting denied permission would result in an Error that is indistinguishable from some other error like broken GPS.

No. Error means the app mustn't work because of error. We need to app work but have no access to the data so It is should be indistinguishable from ***normal operation***.

How about the following: there can be 4 states: initial, granted, denied and faked. When the permission is not asked, it is in initial state. When a user takes action it switches to any of other states. When a user denies, it switches to "fake" state, when a user agrees, it switches to "granted" state. Power users can also switch to "deny" state to explicitly deny to give an app a permission, which will mean that there will be no need to simulate data.  In all "granted", "denied" and "faked" states there should be possible to query the API for data, because if "fake" was used instead of "deny" in most cases devs wouldn't consider "deny" case and it'd useless because it'd crash apps.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/permissions/issues/54#issuecomment-180804933