Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://w3c.github.io/permissions/ below:

Permissions

This specification defines common infrastructure that other specifications can use to interact with browser permissions. These permissions represent a user's choice to allow or deny access to "powerful features" of the platform. For developers, the specification standardizes an API to query the permission state of a powerful feature, and be notified if a permission to use a powerful feature changes state.

This section describes the status of this document at the time of its publication. A list of current W3C publications and the latest revision of this technical report can be found in the W3C standards and drafts index.

This is a work in progress.

This document was published by the Web Application Security Working Group as an Editor's Draft.

Publication as an Editor's Draft does not imply endorsement by W3C and its Members.

This is a draft document and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to cite this document as other than a work in progress.

This document was produced by a group operating under the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent that the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

This document is governed by the 18 August 2025 W3C Process Document.

1. Abstract
2. Status of This Document
3. 1. Introduction
4. 2. Examples of usage
5. 3. Model
   1. 3.1 Permissions
   2. 3.2 Permission Store
   3. 3.3 Powerful features
      1. 3.3.1 Aspects
   4. 3.4 Permissions task source
6. 4. Specifying a powerful feature
7. 5. Algorithms to interface with permissions
   1. 5.1 Reading the current permission state
   2. 5.2 Requesting permission to use a powerful feature
   3. 5.3 Prompt the user to choose
   4. 5.4 Reacting to users revoking permission
8. 6. Permissions API
   1. 6.1 Extensions to the Navigator and WorkerNavigator interfaces
   2. 6.2 Permissions interface
      1. 6.2.1 query() method
   3. 6.3 PermissionStatus interface
      1. 6.3.1 Creating instances
      2. 6.3.2 name attribute
      3. 6.3.3 state attribute
      4. 6.3.4 onchange attribute
      5. 6.3.5 Garbage collection
9. 7. Conformance
10. A. Relationship to the Permissions Policy specification
11. B. Automated testing
    1. B.1 Automated testing with [WebDriver]
       1. B.1.1 Set Permission
    2. B.2 Automated testing with [WebDriver-BiDi]
       1. B.2.1 The permissions Module
          1. B.2.1.1 Definition
          2. B.2.1.2 Types
             1. B.2.1.2.1 The permissions.PermissionDescriptor Type
             2. B.2.1.2.2 The permissions.PermissionState Type
          3. B.2.1.3 Commands
             1. B.2.1.3.1 The permissions.setPermission Command
12. C. Permissions Registry
    1. C.1 Purpose
    2. C.2 Change Process
    3. C.3 Registry table of standardized permissions
    4. C.4 Registry table of provisional permissions
13. D. Privacy considerations
14. E. Security considerations
15. F. IDL Index
16. G. Acknowledgments
17. H. References
    1. H.1 Normative references
    2. H.2 Informative references

This section is non-normative.

Specifications can define features that are explicitly identified as a powerful feature. These features are said to be "powerful" in that they can have significant privacy, security, and performance implications. As such, users rely on user agents to deny sites the ability to use these features until they have given express permission, and usually only granting this ability for a limited amount of time. Express permission to allow a site to use a powerful feature is generally given and controlled through browser UI, as illustrated below.

In this sense, a permission represents the current state of user consent for certain types of features, and particularly "powerful features". Ultimately the user retains control of these permissions and have the ability to manually grant or deny permissions through user preferences. Further, user agents assist users in managing permissions by, for example, hiding and automatically denying certain permission prompts that would otherwise be a nuisance, and automatically expiring granted permissions if a user doesn't visit a website for some time.

This section is non-normative.

This example uses the Permissions API to decide whether local news should be shown using the Geolocation API or with a button offering to add the feature.

const { state } = await navigator.permissions.query({
  name: "geolocation"
});
switch (state) {
  case "granted":
    showLocalNewsWithGeolocation();
    break;
  case "prompt":
    showButtonToEnableLocalNews();
    break;
  case "denied":
    showNationalNews();
    break;
}

This example simultaneously checks the state of the "geolocation" and "notifications" powerful features:

const queryPromises = ["geolocation", "notifications"].map(
  name => navigator.permissions.query({ name })
);
for await (const status of queryPromises) {
  console.log(`${status.name}: ${status.state}`);
}

This example is checking the permission state of the available cameras.

const devices = await navigator.mediaDevices.enumerateDevices();


const queries = devices
  .filter(({ kind }) => kind === "videoinput")
  .map(({ deviceId }) => ({ name: "camera", deviceId }));

const promises = queries.map((queryObj) =>
  navigator.permissions.query(queryObj)
);

try {
  const results = await Promise.all(promises);
  
  results.forEach(({ state }, i) => console.log("Camera", i, state));
} catch (error) {
  console.error(error);
}

This section specifies a model for permissions to use powerful features on the Web platform.

A permission represents a user's decision to allow a web application to use a powerful feature. This decision is represented as a permission state.

Express permission refers to the user granting the web application the ability to use a powerful feature.

Note: Limitations and extensibility

Current Web APIs have different ways to deal with permissions. For example, the Notifications API Standard allows developers to request a permission and check the permission status explicitly. Others expose the status to web pages only when they try to use the API, e.g., the Geolocation which fails if the permission was not granted without allowing the developer to check beforehand.

The solution described in this document is meant to be extensible, but isn't expected to be applicable to all the current and future permissions available in the web platform. Working Groups that are creating specifications whose permission model doesn't fit in the model described in this document should contact the editors by filing an issue.

Conceptually, a permission for a powerful feature can be in one of the following states:

"denied":

The user, or the user agent on the user's behalf, has denied access to this powerful feature. The caller won't be able to use the feature.

"granted":

The user, or the user agent on the user's behalf, has given express permission to use a powerful feature. The caller will be able to use the feature possibly without having the user agent asking the user's permission.

"prompt":

The user has not given express permission to use the feature (i.e., it's the same as "denied"). It also means that if a caller attempts to use the feature, the user agent will either be prompting the user for permission or access to the feature will be "denied".

To ascertain new information about the user's intent, a user agent MAY collect and interpret information about a user's intentions. This information can come from explicit user action, aggregate behavior of both the relevant user and other users, or implicit signals this specification hasn't anticipated.

Note: What constitutes an implicit signal?

The implicit signals could be, for example, the installation status of a web application or frequency and recency of visits. A user that has installed a web application and used it frequently and recently is more likely to trust it. Implementations are advised to exercise caution when relying on implicit signals.

Every permission has a lifetime, which is the duration for which a particular permission remains "granted" before it reverts back to its default state. A lifetime could be until a particular Realm is destroyed, until a particular top-level browsing context is destroyed, a particular amount of time, or be infinite. 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 user-agent defined policy.

Every permission has a default state (usually "prompt"), which is the state that the permission is in when the user has not yet given express permission to use the feature or it has been reset because its lifetime has expired.

The user agent maintains a single permission store which is a list of permission store entries. Each particular entry denoted by its descriptor and key can only appear at most once in this list.

The user agent MAY remove entries from the permission store when their respective permission's lifetime has expired.

A permission store entry is a tuple of PermissionDescriptor descriptor, permission key key, and state state.

A permission key has its type defined by a feature's permission key type.

Note

A powerful feature is a web platform feature (usually an API) for which a user gives express permission before the feature can be used. Except for a few notable exceptions (e.g., the Notifications API Standard), most powerful features are also policy-controlled features. For powerful features that are also policy-controlled features, [Permissions-Policy] controls whether a document is allowed to use a given feature. That is, a powerful feature can only request express permission from a user if the document has permission delegated to it via the corresponding policy-controlled feature (see example below). Subsequent access to the feature is determined by the user having "granted" permission, or by satisfying some criteria that is equivalent to a permission grant.

This example shows how the permissions policy set through the allow attribute controls whether the iframe is allowed to use a powerful feature. Because "geolocation" is allowed, the iframe's document can request permission from the user to use the Geolocation (i.e., it will prompt the user for express permission to access their location information). However, requesting permission to use any other feature will be automatically denied, because they are not listed in the allow attribute.

<iframe src="https://example.com/" allow="geolocation">
</iframe>

See A. Relationship to the Permissions Policy specification for more information.

A powerful feature is identified by its name, which is a string literal (e.g., "geolocation").

The user agent tracks which powerful features the user has permission to use via the environment settings object.

Each powerful feature can define zero or more additional aspects. An aspect is defined as WebIDL dictionary that inherits from PermissionDescriptor and serves as a WebIDL interface's permission descriptor type.

A hypothetical powerful feature "food detector API" has two aspects that allow sensing taste and smell. So, a specification would define a new WebIDL interface that inherits PermissionDescriptor:

dictionary SensesPermissionDescriptor : PermissionDescriptor {
  boolean canSmell = false;
  boolean canTaste = false;
};

Which would then be queried via the API in the following way:

const status = await navigator.permissions.query({
  name: "senses",
  canSmell: true,
});

A user can restrict the "senses" powerful feature to only "taste", in which case the PermissionStatus's state above would be "denied" .

The permissions task source is a task source used to perform permissions-related tasks in this specification.

When a conforming specification specifies a powerful feature it:

1. MUST give the powerful feature a name in the form of a ascii lowercase string.
2. MAY define a permission descriptor type that inherits from PermissionDescriptor.
3. MAY define zero or more aspects.
4. MAY override the algorithms and types given below if the defaults are not suitable for a particular powerful feature.
5. MUST register the powerful feature in the Permissions Registry.

Registering the newly specified powerful features in the Permissions Registry gives this Working Group an opportunity to provide feedback and check that integration with this specification is done effectively.

A permission descriptor type:

PermissionDescriptor or one of its subtypes. If unspecified, this defaults to PermissionDescriptor.

The feature can define a partial order on descriptor instances. If descriptorA is stronger than descriptorB, then if descriptorA's permission state is "granted", descriptorB's permission state must also be "granted", and if descriptorB's permission state is "denied", descriptorA's permission state must also be "denied".

Example 6: A permission descriptor that defines a partial order

{name: "midi", sysex: true} ("midi-with-sysex") is stronger than {name: "midi", sysex: false} ("midi-without-sysex"), so if the user denies access to midi-without-sysex, the UA must also deny access to midi-with-sysex, and similarly if the user grants access to midi-with-sysex, the user agent must also grant access to midi-without-sysex.

permission state constraints:

Constraints on the values that the user agent can return as a descriptor's permission state. Defaults to no constraints beyond the user's intent.

:

Some powerful features have more information associated with them than just a PermissionState. Each of these features defines an extra permission data type.

Note

For example, getUserMedia() needs to determine which cameras the user has granted permission to access.

If specified, the extra permission data algorithm is usable for this feature.

Optional :

Constraints on the values that the user agent can return as a powerful feature's extra permission data. Defaults to no constraints beyond the user's intent.

A permission result type:

PermissionStatus or one of its subtypes. If unspecified, this defaults to PermissionStatus.

A permission query algorithm:

Takes an instance of the permission descriptor type and a new or existing instance of the permission result type, and updates the permission result type instance with the query result. Used by Permissions' query(permissionDesc) method and the PermissionStatus update steps. If unspecified, this defaults to the default permission query algorithm.

A permission key type:

The type of permission key used by the feature. Defaults to origin. A feature that specifies a custom permission key type MUST also specify a permission key generation algorithm.

A permission key generation algorithm:

Takes an origin origin and an origin embedded origin, and returns a new permission key. If unspecified, this defaults to the default permission key generation algorithm. A feature that specifies a custom permission key generation algorithm MUST also specify a permission key comparison algorithm.

The default permission key generation algorithm, given an origin origin and an origin embedded origin, runs the following steps:

1. Return origin.

Note: Permission Delegation

Most powerful features grant permission to the top-level origin and delegate access to the requesting document via Permissions Policy. This is known as permission delegation.

A permission key comparison algorithm:

Takes two permission keys and returns a boolean that shows whether the two keys are equal. If unspecified, this defaults to the default permission key comparison algorithm.

The default permission key comparison algorithm, given permission keys key1 and key2, runs the following steps:

1. Return key1 is same origin with key2.

A permission revocation algorithm:

Takes no arguments. Updates any other parts of the implementation that need to be kept in sync with changes in the results of permission states or extra permission data.

If unspecified, this defaults to running react to the user revoking permission.

A permission lifetime:

Specifications that define one or more powerful features SHOULD suggest a 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 lifetime is specified, the user agent provides one.

When the permission lifetime expires for an origin:

1. Set the permission back to its default permission state (e.g., by setting it back to "prompt").
2. For each browsing context associated with the origin (if any), queue a global task on the permissions task source with the browsing context's global object to run the permission revocation algorithm.

Note: Determining the lifetime of a permission

For particularly privacy-sensitive features, such as Media Capture and Streams, which can provide a web application access to a user's camera and microphone, some user agents expire a permission grant as soon as a browser tab is closed or navigated. For other features, like the Geolocation, user agents are known to offer a choice of only granting the permission for the session, or for one day. Others, like the Notifications API Standard and Push API APIs, remember a user's decision indefinitely or until the user manually revokes the permission. Note that permission lifetimes can vary significantly between user agents.

Finding the right balance for the lifetime of a permission requires a lot of thought and experimentation, and often evolves over a period of years. Implementers are encouraged to work with their UX security teams to find the right balance between ease of access to a powerful feature (i.e., reducing the number of permission prompts), respecting a user's privacy, and making users aware when a web application is making use of a particular powerful feature (e.g., via some visual or auditory UI indicator).

If you are unsure about what lifetime to suggest for a powerful feature, please contact the Privacy Interest Group for guidance.

Default permission state:

An PermissionState value that serves as a permission's default state of a powerful feature.

If not specified, the permission's default state is "prompt".

A default powerful feature is a powerful feature with all of the above types and algorithms defaulted.

As a shorthand, a DOMString name's permission state is the permission state of a PermissionDescriptor with its name member set to name.

As a shorthand, requesting permission to use a DOMString name, is the same as requesting permission to use a PermissionDescriptor with its name member set to name.

To prompt the user to choose one or more options associated with a given descriptor and an optional boolean allowMultiple (default false), the user agent must perform the following steps. This algorithm returns either "denied" or the user's selection.

1. If descriptor's permission state is "denied", return "denied" and abort these steps.
2. If descriptor's permission state is "granted", the user agent may return one (or more if allowMultiple is true) of options chosen by the user and abort these steps. If the user agent returns without prompting, then subsequent prompts for the user to choose from the same set of options with the same descriptor must return the same option(s), unless the user agent receives new information about the user's intent.
3. Ask the user to choose one or more options or deny permission, and wait for them to choose:
   1. If the calling algorithm specified extra information to include in the prompt, include it.
   2. If allowMultiple is false, restrict selection to a single item from options; otherwise, any number may be selected by the user.
4. If the user chose one or more options, return them; otherwise return "denied".

   Note

   This is intentionally vague about the details of the permission UI and how the user agent infers user intent. User agents should be able to explore lots of UI within this framework (e.g., a permission prompt could time out and automatically return "denied" without the user making an explicit selection).

As a shorthand, prompting the user to choose from options associated with a DOMString name, is the same as prompting the user to choose from those options associated with a PermissionDescriptor with its name member set to name.

This feature is in all major engines.

[Exposed=(Window)]
partial interface Navigator {
  [SameObject] readonly attribute Permissions permissions;
};

[Exposed=(Worker)]
partial interface WorkerNavigator {
  [SameObject] readonly attribute Permissions permissions;
};

This feature is in all major engines.

[Exposed=(Window,Worker)]
interface Permissions {
  Promise<PermissionStatus> query(object permissionDesc);
};

dictionary PermissionDescriptor {
  required DOMString name;
};

This feature is in all major engines.

When the query() method is invoked, the user agent MUST run the following query a permission algorithm, passing the parameter permissionDesc:

1. If this's relevant global object is a Window object, then:
   1. If the current settings object's associated Document is not fully active, return a promise rejected with an "InvalidStateError" DOMException.
2. Let rootDesc be the object permissionDesc refers to, converted to an IDL value of type PermissionDescriptor.
3. If the conversion throws an exception, return a promise rejected with that exception.
4. If rootDesc["name"] is not supported, return a promise rejected with a TypeError.

   Note: Why is this not an enum?

   This is deliberately designed to work the same as WebIDL's enumeration (enum) and implementers are encouraged to use their own custom enum here. The reason this is not an enum in the specification is that browsers vary greatly in the powerful features they support. Using a DOMString to identify a powerful feature gives implementers the freedom to pick and choose which of the powerful features from the Permissions Registry they wish to support.

5. Let typedDescriptor be the object permissionDesc refers to, converted to an IDL value of rootDesc's name's permission descriptor type.
6. If the conversion throws an exception, return a promise rejected with that exception.
7. Let promise be a new promise.
8. Return promise and continue in parallel:
   1. Let status be create a PermissionStatus with typedDescriptor.
   2. Let query be status's [[query]] internal slot.
   3. Run query's name's permission query algorithm, passing query and status.
   4. Queue a global task on the permissions task source with this's relevant global object to resolve promise with status.

This feature is in all major engines.

[Exposed=(Window,Worker)]
interface PermissionStatus : EventTarget {
  readonly attribute PermissionState state;
  readonly attribute DOMString name;
  attribute EventHandler onchange;
};

enum PermissionState {
  "granted",
  "denied",
  "prompt",
};

PermissionStatus instances are created with a [[query]] internal slot, which is an instance of a feature's permission descriptor type.

The "granted", "denied", and "prompt" enum values represent the concepts of "granted", "denied", and "prompt" respectively.

To create a PermissionStatus for a given PermissionDescriptor permissionDesc:

1. Let name be permissionDesc's name.
2. Assert: The feature identified by name is supported by the user agent.
3. Let status be a new instance of the permission result type identified by name:
   1. Initialize status's [[query]] internal slot to permissionDesc.
   2. Initialize status's name to name.
4. Return status.

This feature is in all major engines.

The name attribute returns the value it was initialized to.

This feature is in all major engines.

The state attribute returns the latest value that was set on the current instance.

This feature is in all major engines.

The onchange attribute is an event handler whose corresponding event handler event type is change.

A PermissionStatus object MUST NOT be garbage collected if it has an event listener whose type is change.

As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.

The key words MAY, MUST, MUST NOT, OPTIONAL, and SHOULD in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

Two classes of product can claim conformance to this specification: user agents and other specifications (i.e., a technical report that specifies a powerful feature in a manner that conforms to the requirements of this specification).

This section is non-normative.

Although both this specification and the Permissions Policy specification deal with "permissions", each specification serves a distinct purpose in the platform. Nevertheless, the two specifications do explicitly overlap.

On the one hand, this specification exclusively concerns itself with powerful features whose access is managed through a user-agent mediated permissions UI (i.e., permissions where the user gives express consent before that feature can be used, and where the user retains the ability to deny that permission at any time for any reason). These powerful features are registered in the Permissions Registry.

On the other hand, the Permissions Policy specification allows developers to selectively enable and disable policy-controlled features through a "permissions policy" (be it a HTTP header or the allow attribute). In that sense, the Permissions Policy subsumes this specification in that Permissions Policy governs whether a feature is available at all, independently of this specification. These policy-controlled features are also registered in the Permissions Registry.

A powerful feature that has been disabled by the Permissions Policy specification always has its permission state reflected as "denied" by this specification. This occurs because reading the current permission relies on [HTML]'s "allowed to use" check, which itself calls into the Permissions Policy specification. Important to note here is the sharing of permission names across both specifications. Both this specification and the Permissions Policy specification rely on other specifications defining the names of the permission and name, and they are usually named the same thing (e.g., "geolocation" of the Geolocation, and so on).

Finally, it's not possible for a powerful feature to ever become "granted" through any means provided by the Permissions Policy specification. The only way that a powerful feature can be "granted" is by the user giving express permission or by some user agent policy.

For the purposes of user-agent automation and application testing, this document defines extensions to the [WebDriver] and [WebDriver-BiDi] specifications. It is OPTIONAL for a user agent to support them.

dictionary PermissionSetParameters {
  required object descriptor;
  required PermissionState state;
};

This document defines the following extension commands for the [WebDriver] specification.

The Set Permission extension command simulates user modification of a PermissionDescriptor's permission state.

The remote end steps are:

1. Let parametersDict be the parameters argument, converted to an IDL value of type PermissionSetParameters. If this throws an exception, return an invalid argument error.
2. If parametersDict.state is an inappropriate permission state for any implementation-defined reason, return an invalid argument error.
3. Let rootDesc be parametersDict.descriptor.
4. Let typedDescriptor be the object rootDesc refers to, converted to an IDL value of permission descriptor type matching the result of Get(rootDesc, "name"). If this throws an exception, return a invalid argument error.
5. Set a permission with typedDescriptor and parametersDict.state.
6. Return success with data null.

To set permission for {name: "midi", sysex: true} of the current settings object of the session with ID 23 to "granted", the local end would POST to /session/23/permissions with the body:

{
  "descriptor": {
    "name": "midi",
    "sysex": true
  },
  "state": "granted"
}

This document defines the following extension modules for the [WebDriver-BiDi] specification.

The permissions module contains commands for managing the remote end browser permissions.

{^remote end definition^}

PermissionsCommand = (
  permissions.setPermission
)

permissions.PermissionDescriptor = {
  name: text,
}

The permissions.PermissionDescriptor type represents a PermissionDescriptor.

permissions.PermissionState = "granted" / "denied" / "prompt"

The permissions.PermissionState type represents a PermissionState.

The Set Permission command simulates user modification of a PermissionDescriptor's permission state.

Command Type

permissions.setPermission = (
  method: "permissions.setPermission",
  params: permissions.SetPermissionParameters
)

permissions.SetPermissionParameters = {
  descriptor: permissions.PermissionDescriptor,
  state: permissions.PermissionState,
  origin: text,
  ? embeddedOrigin: text,
  ? userContext: text,
}

Result Type

EmptyResult

The remote end steps with session and command parameters are:

1. Let descriptor be the value of the descriptor field of command parameters.
2. Let permission name be the value of the name field of descriptor representing name.
3. Let state be the value of the state field of command parameters.
4. Let user context id be the value of the userContext field of command parameters, if present, and default otherwise.
5. If state is an inappropriate permission state for any implementation-defined reason, return error with error code invalid argument.
6. Let typedDescriptor be the object descriptor refers to, converted to an IDL value (descriptor, state) of PermissionSetParameters permission name's permission descriptor type. If this conversion throws an exception, return error with error code invalid argument.
7. Let origin be the value of the origin field of command parameters.
8. Let embedded origin be the value of the embeddedOrigin field of command parameters, if present, and origin otherwise.
9. Let key be the result of generating a permission key for descriptor with origin and embedded origin.
10. Let user agent be the user agent that represents the user context with the id user context id.
11. Set a permission with typedDescriptor, state, key, and user agent.
12. Return success with data null.

This section is non-normative.

This W3C Registry provides a centralized place to find the policy-controlled features and/or powerful features of the web platform. Through the change process it also helps assure permissions in the platform are consistently specified across various specifications.

By splitting the registry into standardized permissions and provisional permissions, the registry also provides a way to track the status of these features.

The change process for adding and/or updating this registry is as follows:

1. If necessary, add a "Permissions Policy" section to your specification which includes the following:
   1. The string that identifies the policy controlled feature (e.g., "super-awesome"). Make sure the string is linkable by wrapping it a dfn element.
   2. The default allowlist value (e.g. 'self').

      An typical example that would meet this criteria:

      The Super Awesome API defines a policy-controlled feature identified by the string "super-awesome". Its default allowlist is 'self'.

2. Determine if your feature meets the definition of a powerful feature (i.e., requires express permission to be used). If it does:
   1. Specify a powerful feature in your specification in conformance with the Permissions specification.
3. Modify either the table of standardized permissions or the table of provisional permissions filling out each column with the required information.
4. Submit a pull request to the Powerful Features Registry Repository on GitHub with your changes. The maintainers of the repository will review your pull request and check that everything integrates properly.

For a permission to appear in the table of standardized permissions, and thus be considered a standardized permission, it needs to meet the following criteria:

• Implemented and demonstrably interoperable in at least two browser engines (e.g., has accompanying Web Platform Tests).
• Is specified in published as technical report by a W3C Working Group with maturity of first public working draft or above, or is published by the WHATWG as a standard.

Each permission is identified by a unique literal string. In the case of Permissions Policy, the string identifies a policy-controlled features. Similarly, in the Permissions specification the string identifies a powerful feature.

Provisional permissions are permissions that are not yet standardized (i.e., they are either experimental, still in the incubation phase, or are only implemented in a single browser engine).

An adversary could use a permission state as an element in creating a "fingerprint" corresponding to an end-user. Although an adversary can already determine the state of a permission by actually using the API, that often leads to a UI prompt being presented to the end-user (if the permission was not already "granted"). Even though this API doesn't expose new fingerprinting information to websites, it makes it easier for an adversary to have discreet access to this information.

A user agent SHOULD provide a means for the user to review, update, and reset the permission state of powerful features associated with an origin.

There are no documented security considerations at this time. Readers are instead encouraged to read section D. Privacy considerations.

[Exposed=(Window)]
partial interface Navigator {
  [SameObject] readonly attribute Permissions permissions;
};

[Exposed=(Worker)]
partial interface WorkerNavigator {
  [SameObject] readonly attribute Permissions permissions;
};

[Exposed=(Window,Worker)]
interface Permissions {
  Promise<PermissionStatus> query(object permissionDesc);
};

dictionary PermissionDescriptor {
  required DOMString name;
};

[Exposed=(Window,Worker)]
interface PermissionStatus : EventTarget {
  readonly attribute PermissionState state;
  readonly attribute DOMString name;
  attribute EventHandler onchange;
};

enum PermissionState {
  "granted",
  "denied",
  "prompt",
};

dictionary PermissionSetParameters {
  required object descriptor;
  required PermissionState state;
};

This section is non-normative.

The editors would like to thank Adrienne Porter Felt, Anne van Kesteren, Domenic Denicola, Jake Archibald and Wendy Seltzer for their help with the API design and editorial work.

[dom]

DOM Standard. Anne van Kesteren. WHATWG. Living Standard. URL: https://dom.spec.whatwg.org/

[ecma-262]

ECMAScript Language Specification. Ecma International. URL: https://tc39.es/ecma262/multipage/

[HTML]

HTML Standard. Anne van Kesteren; Domenic Denicola; Dominic Farolino; Ian Hickson; Philip Jägenstedt; Simon Pieters. WHATWG. Living Standard. URL: https://html.spec.whatwg.org/multipage/

[infra]

Infra Standard. Anne van Kesteren; Domenic Denicola. WHATWG. Living Standard. URL: https://infra.spec.whatwg.org/

[Notifications]

Notifications API Standard. Anne van Kesteren. WHATWG. Living Standard. URL: https://notifications.spec.whatwg.org/

[Permissions-Policy]

Permissions Policy. Ian Clelland. W3C. 6 August 2025. W3C Working Draft. URL: https://www.w3.org/TR/permissions-policy-1/

[permissions-registry]

Permissions Registry. W3C. Draft Registry. URL: https://w3c.github.io/permissions-registry/

[RFC2119]

Key words for use in RFCs to Indicate Requirement Levels. S. Bradner. IETF. March 1997. Best Current Practice. URL: https://www.rfc-editor.org/rfc/rfc2119

[RFC8174]

Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words. B. Leiba. IETF. May 2017. Best Current Practice. URL: https://www.rfc-editor.org/rfc/rfc8174

[WebDriver]

WebDriver. Simon Stewart; David Burns. W3C. 5 June 2018. W3C Recommendation. URL: https://www.w3.org/TR/webdriver1/

[WebDriver-BiDi]

WebDriver BiDi. James Graham; Alex Rudenko; Maksim Sadym. W3C. 1 October 2025. W3C Working Draft. URL: https://www.w3.org/TR/webdriver-bidi/

[webdriver2]

WebDriver. Simon Stewart; David Burns. W3C. 8 September 2025. W3C Working Draft. URL: https://www.w3.org/TR/webdriver2/

[WEBIDL]

Web IDL Standard. Edgar Chen; Timothy Gu. WHATWG. Living Standard. URL: https://webidl.spec.whatwg.org/

[appmanifest]

Web Application Manifest. Marcos Caceres; Kenneth Christiansen; Diego Gonzalez-Zuniga; Daniel Murphy; Christian Liebel. W3C. 3 September 2025. W3C Working Draft. URL: https://www.w3.org/TR/appmanifest/

[Geolocation]

Geolocation. Marcos Caceres; Reilly Grant. W3C. 23 September 2025. W3C Recommendation. URL: https://www.w3.org/TR/geolocation/

[GETUSERMEDIA]

Media Capture and Streams. Cullen Jennings; Jan-Ivar Bruaroey; Henrik Boström; youenn fablet. W3C. 25 September 2025. CRD. URL: https://www.w3.org/TR/mediacapture-streams/

[local-font-access]

Local Font Access API. W3C. Draft Community Group Report. URL: https://wicg.github.io/local-font-access/

[orientation-event]

Device Orientation and Motion. Reilly Grant; Marcos Caceres. W3C. 12 February 2025. CRD. URL: https://www.w3.org/TR/orientation-event/

[Permissions]

Permissions. Marcos Caceres; Mike Taylor. W3C. 26 September 2025. W3C Working Draft. URL: https://www.w3.org/TR/permissions/

[push-api]

Push API. Marcos Caceres; Kagami Rosylight. W3C. 25 September 2025. W3C Working Draft. URL: https://www.w3.org/TR/push-api/

[w3c-process]

W3C Process Document. Elika J. Etemad (fantasai); Florian Rivoal. W3C. 18 August 2025. URL: https://www.w3.org/policies/process/

Web Share API. Marcos Caceres; Eric Willigers; Matt Giuca. W3C. 30 May 2023. W3C Recommendation. URL: https://www.w3.org/TR/web-share/

[window-management]

Window Management. Joshua Bell; Mike Wasserman. W3C. 7 June 2024. W3C Working Draft. URL: https://www.w3.org/TR/window-management/

↑

Referenced in:

• Not referenced in this document.

Referenced in:

• Not referenced in this document.

Referenced in:

• Not referenced in this document.

Referenced in:

• Not referenced in this document.

Referenced in:

• Not referenced in this document.

Referenced in:

• Not referenced in this document.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.5