focus-without-user-activation - Missing compatibility data
Maintainers usually reply within 1 day
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
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?
- HTML specification
- Chrome Platform Status
- Chromium implementation tracking bug
- Intent to Ship discussion
- MDN documentation issue #37532
- web-features issue #4487
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
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mdn/browser-compat-data
-
Web extensions - Safari Technology Preview 257 data and the message_serialization manifest keyPossibly taken @xeenon claimed this today. Openneeds triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mdn/browser-compat-data#31192 ·
Maintainers usually reply within 1 day
-
api.WGSLLanguageFeatures - Firefox supports three featuresPossibly taken @Manishram-ai claimed this 1 day ago. Opendata:api needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
mdn/browser-compat-data#31175 ·
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
mdn/browser-compat-data#31069 · 1 comment ·
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mdn/browser-compat-data#31057 · 2 comments ·
Maintainers usually reply within 1 day
-
api.Window.devicePixelRatio - Does change with page zoom in Safari (webkit)Possibly taken @Manishram-ai claimed this 1 day ago. Opendata:api needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
mdn/browser-compat-data#31039 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
All issues in mdn/browser-compat-data
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
molgenis/molgenis-emx2#7059 ·
Maintainers usually reply within 1 day
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
needs-format
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Niko1221/Strata#6251 · 1 comment ·
Maintainers usually reply within 5 days
-
area: plugins documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
CatVinci-Studio/Textus#727 ·
Maintainers usually reply within 1 day