Repository navigation
Description
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
- Main WPT search: https://wpt.fyi/results/?label=master&label=experimental&aligned&q=permission%20policy
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:
-
Multiple bug reports:
- Chromium 765923: https://bugs.chromium.org/p/chromium/issues/detail?id=765923
- Bugzilla 1635700: https://bugzilla.mozilla.org/show_bug.cgi?id=1635700
- Bugzilla 1653170: https://bugzilla.mozilla.org/show_bug.cgi?id=1653170
-
Posts on StackOverflow and GitHub issues citing unexpected behavior.
-
State of JS and HTML surveys show developer demand for features depending on Permissions Policy (e.g., Web Share API, Clipboard).
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
- Web Share API Interop 2024 proposal: Add all failing tests from Previous Focus Areas as separate area to 2025 score. #728
- Permissions Policy interop issue tracking: Permissions Policy interop #1082
- MDN documentation: https://developer.mozilla.org/en-US/docs/Web/HTTP/Permissions_Policy
- wpt.fyi filtered results: https://wpt.fyi/results/?label=master&label=experimental&aligned&q=permission%20policy
Rationale
No response
Investigation Roadmap
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
wpt-interop commentedon Feb 12, 2026
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.