- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 10 Feb 2022 13:33:29 -0800
- To: Marcos Caceres <marcos@marcosc.com>
- Cc: spec-prod <spec-prod@w3.org>, Dominique Hazaël-Massieux <dom@w3.org>, Francois Daoust <fd@w3.org>
On Wed, Feb 9, 2022 at 8:13 PM Marcos Caceres <marcos@marcosc.com> wrote: > For example, the token string "geolocation" can be used by both the in different ways by different technologies: > > * Permissions-Policy HTTP header > * iframe's allow= attribute, where HTML checks if a document is "allowed to use" token string. > * In the Permissions spec, when .query() is called, it checks if the feature identified by the token string is supported. > * And so on... > > I'd like propose that we elevate these token strings from being a "concept" type to an explicit "permission" definition type. So long as it is indeed common to use the exact same string in all the situations, then yeah, I've got no problem with a new definition type. ~TJ
Received on Thursday, 10 February 2022 21:33:59 UTC