- From: Marcos Cáceres <notifications@github.com>
- Date: Thu, 11 Nov 2021 17:18:33 -0800
- To: w3c/permissions <permissions@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/permissions/pull/287/review/804339597@github.com>
@marcoscaceres commented on this pull request. > + Every [=permission=] has a [=permission/lifetime=], which is the duration for which + a particular permission remains [=permission/granted=] before it reverts back to + its default [=permission state=]. The lifetime is negotiated between the end-user + and the [=user agent=] when the user gives [=express permission=] to use a + [=feature=] - usually via some permission UI or policy. + </p> + <p> + Specifications that identify themselves as a [=powerful feature=] SHOULD suggest a + [=permission=] [=permission/lifetime=] that is best suited for the particular + feature. Some guidance on determining the lifetime of a permission is noted below, + with a strong emphasis on user privacy. If no [=permission/lifetime=] is specified, + the user agent provides one. + </p> + <p> + When the permission [=permission/lifetime=] expires for an origin, and if there are + [=browsing contexts=] present pertaining to the [=permission=]'s associated origin, No... I was hesitant to use that word. I'm open to suggestions as to how to make that association (I'll give that some further thought too). -- 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/pull/287#discussion_r747916546
Received on Friday, 12 November 2021 01:18:46 UTC