- From: Mike Taylor <notifications@github.com>
- Date: Fri, 12 Nov 2021 14:49:36 -0800
- To: w3c/permissions <permissions@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/permissions/pull/287/review/805281563@github.com>
@miketaylr commented on this pull request. Looks pretty good to me, pending @jyasskin's comments. > + 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, I think we're trying to say, if you're the top-level browsing context for a given origin and have any ancestor browsing contexts, revoke permission for all browsing contexts? I guess https://html.spec.whatwg.org/#nested-browsing-contexts gives you most of what you need. -- 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#pullrequestreview-805281563
Received on Friday, 12 November 2021 22:49:48 UTC