Re: [w3c/permissions] Support minimizable request UI with permissions.request() (#76)

> Having a request with two answers is very odd. For users and developers. I think the behaviour Firefox has is broken: if the permission gets hidden, the request was dismissed.

It's not two answers though. "default" isn't an answer, it's just notifying about a state change so it doesn't fit as a resolution.

> If the user comes back to take an action on the request, it's not different from the user going to the settings and approve/deny a permission.

I don't think we should expect UAs to have UI to proactively grant permission for a site. At least in Fx we're planning to only allow revoking from the control center (address bar panel), not allowing. This sounds like you're in favour of my suggestion… see below. I agree that all permission changes (in the prompt or from other settings UI should be treated the same and that's why I propose that the `change` handler should be the way to find out about them, not a separate .request() mechanism (e.g. return value).

> I understand where you are coming from but I do not think we should make the Permissions API less developer friendly in order to support an odd UI feature that Firefox has.

What I'm proposing for the API is more developer friendly as it means that developers by-default catch the permission changes that happen outside the request too. It means there is only one way to know about permission changes instead of two as there currently is in the spec (from request and change).

---
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/76#issuecomment-210093951