Re: [w3c/permissions] Model temporary permissions better (#86)

I see @jyasskin 's point now, which is that temporary settings (what I'd like to call `'allowed temporarily'` and `'blocked temporarily'`) will typically come from the current browsing session (tab), rather than the origin where persistent settings come from. Not just in Safari, but in Firefox too. It's harder to see in Firefox, if you're just going by whether you get prompted or not - because Firefox prompts relentlessly - but if you look from where I borrowed the terms, the Firefox-user-facing [page-info mockups](https://mozilla.invisionapp.com/share/PC3Y0QSRK#/screens/96290112), it seems clear that from a browser user's POV at least, there is interest in seeing both what's been granted temporarily in a given tab, overlaid with what's been granted permanently to the origin. Two tabs of the same origin therefore, may differ in what's shown in their respective page-info dropdowns. Like in the Safari example - hypothetically if Safari had a page-info dropdown - one tab might show `'al
 lowed temporarily'` (because of it's local state) while the other would show nothing (aka `'prompt'` in that UX design), which is reflective of default the shared origin setting.

My apologies if mixing in browser-user-facing UX is not helpful. I understand that site developers may have different needs from browser-users, and might not even care whether access is permanent or temporary, but I'm thinking it can't hurt, and it seems to solve the "inconsistency bug" @mounirlamouri [brought up](https://github.com/w3c/permissions/issues/93#issuecomment-215372312) at least, by giving us unambiguous return values.

---
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/86#issuecomment-215599666