Re: [w3c/permissions] Consider removing "lifetime" (Issue #391)

I'm a bit on the fence about this.

To (hopefully) help with your concern about implementation in Chromium, @tungnh28, what the spec is describing is an API surface that the browser should support for new and existing features building on top of permissions. How lifetimes are implemented in Chromium doesn't really matter as long as a feature could have e.g. a custom "lifetime" key which would then result in the same web-observable behavior across browsers.

However, I also feel like lifetime/expiry might be a common mechanism that we want features to think about, and that we want to promote usage of. Requiring feature specs to do the extra work of adding a custom key for lifetimes seems to go against that goal.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/permissions/issues/391#issuecomment-1330769873
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/permissions/issues/391/1330769873@github.com>