Skip to content

Permissions Policy #1132

Closed
Closed

Description

@BearCooder

Description

Interop 2026 Investigation Effort Proposal: Permissions Policy

In last years proposal for Web Share the issue came up with Permissions Policy: #464
I first proposed an docus are proposal this year: #1082 but I think now that an investigation effort proposal for this makes more sense.

Feature Name

Permissions Policy

Summary

Permissions Policy is a foundational browser mechanism that allows developers to control which features and APIs are available to web pages and frames. It plays a critical role in enabling or restricting access to features like Web Share API, Clipboard API, Geolocation, Camera/Microphone access, and more.

Despite its importance, browser support for Permissions Policy is inconsistent, and tests are difficult to interpret due to being interleaved with other features. This proposal suggests an Investigation Effort to:

  • Clarify the scope of Permissions Policy testing.
  • Ensure test coverage accurately reflects Permissions Policy behavior.
  • Enable more consistent implementation across browsers.

Specification

MDN Documentation

Test Coverage

Note: Many tests reflect incidental use of Permissions Policy in unrelated APIs. A scoped test set needs to be curated.

As jgraham commented here: #1082 (comment):

“It would be quite helpful to have a more minimal list of tests which match the intended scope of the proposal.”

Developer Pain and Sentiment

Permissions Policy inconsistencies cause confusion for developers using:

  • Web Share API
  • Clipboard API
  • Fullscreen API
  • Geolocation API
  • Device APIs (Camera, Microphone)
  • Iframe sandboxing and third-party embedders

Evidence:

This effort seeks to identify and isolate Permissions Policy tests, analyze gaps in support across browsers, and recommend ways to ensure consistent and predictable behavior.

Goals of Investigation

  • Build a minimal, focused test suite for core Permissions Policy features.
  • Identify areas of missing or incomplete support across major engines.
  • Clarify dependencies between Permissions Policy and other features (e.g., Web Share).

Additional Info

Rationale

No response

Investigation Roadmap

No response

Activity

  1. wpt-interop commented on Feb 12, 2026

    @wpt-interop
    Collaborator

    Thank you for proposing Permissions Policy for Interop 2026.

    We want to let you know it was not selected to be part of Interop this year.

    On behalf of the entire Interop team, thank you for submitting it for consideration. We got many more proposals than we could include in this year's project, necessitating some difficult choices. Please note this should not be taken as a comment on the technology as a whole, or our willingness to consider it for Interop in the future. We appreciate the work you put into your proposal, and would welcome your participation in future rounds of Interop.

    Posted on behalf of the Interop team.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions