- From: Anne van Kesteren <notifications@github.com>
- Date: Tue, 29 Nov 2022 02:55:03 -0800
- To: w3c/permissions <permissions@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 29 November 2022 10:55:19 UTC
It's not clear to me what the value add is. If a permission wanted to limit its lifetime or scope in some way it can define its own key. #390 adds infrastructure for this and "storage-access" will make use of it. If a permission wants to make a recommendation (but not require) that a user agent limits its lifetime in some way it can recommend they use an implementation-defined key as will be allowed if we do the above. If a lot of permissions end up doing that in a similar fashion it might make sense to add some kind of abstraction, but 1) lifetime isn't that and 2) this doesn't appear to be the case. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/permissions/issues/391#issuecomment-1330444093 You are receiving this because you are subscribed to this thread. Message ID: <w3c/permissions/issues/391/1330444093@github.com>
Received on Tuesday, 29 November 2022 10:55:19 UTC