Re: [permissions] Should 'prompt' be renamed as 'default'? (#12)

> If your algorithm depends on some parameters like origin, previous usage, type of network, there are no reasons why .query() shouldn't work.

The issue is that when you register for a bg sync, we don't know what these parameters will be when the bg sync opportunity arise.

Suppose that a user is using a web app, called Miracle Deluxe, on a flaky connection. One of his action failed because of network issues. The web app would then register for a one-off bg sync opportunity [1].

[2] A couple of hours later, the user arrives at his work place and his device connects to the office's WiFi. The user might not want to let his employer knows that he's using Miracle Deluxe. In the permission model being explored, the user agent would notice that the user never accessed Miracle Deluxe on this particular network. The user agent would prompt in that case. 

[3] The user comes back home and his device connects to his home WiFi. The user agent would notice that the user has accessed Miracle Deluxe on this network and decide to grant a no prompt one-off bg sync.

[4] Same scenario but with a non sensitive web app, called Everyday Happenings. Let's assume that the user has told his user agent to always allow bg sync for Everyday Happenings.

Query at [1]: "unknown"
Query at [2]: "prompt"
Query at [3]: "granted"
Query by Everyday Happenings: "granted"

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