focus-without-user-activation - Missing compatibility data

Open Beginner friendly
#30,985 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Marwan-verse is already working on this.

Since Oct 28, 2026.

  • #30991 by @Marwan-verse — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
html, json
Domain
documentation

Research direction

Start with http/headers/Permissions-Policy.json and compare nearby Permissions Policy entries to learn the expected compatibility data structure. Check the linked specification and browser sources for support versions and flag requirements, including the stated cross-origin autofocus limitation. Done means adding focus-without-user-activation with the specification link and verified browser support data.

Written by the indexing model from the issue text.

Description

needs triage
What type of issue is this?

Missing compatibility data

What information was incorrect, unhelpful, or incomplete?

The focus-without-user-activation Permissions Policy directive is missing from BCD. There is no entry in http/headers/Permissions-Policy.json so its browser compatibility is not represented.

What browsers does this problem apply to, if applicable?

Chromium (Chrome, Edge 79+, Opera, Samsung Browser)

What did you expect to see?

A compatibility entry at http.headers.Permissions-Policy.focus-without-user-activation, including the specification link, browser support versions, and any applicable flag requirements.

This policy lets embedders restrict programmatic focus from embedded documents without blocking user-initiated focus.

Did you test this? If so, how?

Yes, there are WPT tests for it, Microsoft Teams is rolling it out to production, and manually checked in Chrome/Edge canary.

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
Do you have anything more you want to share?

The web-features maintainer identified this missing BCD key and requested a BCD issue or PR. Adding it would support the corresponding web-features entry and MDN compatibility tables.

One implementation detail to account for: allowing this policy does not lift Chromium’s existing restriction on cross-origin autofocus. That behavior is discussed in WHATWG HTML #13105. This is mentioned in the intent to ship discussion.

MDN URL

No response

MDN metadata

No response

Dominant language
JSON
Stars
5.8k
Forks
2.7k
Avg merge
2d 20h
Merged PRs (30d)
160

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mdn/browser-compat-data

All issues in mdn/browser-compat-data

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.