Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add focus-without-user-activation permissions policy #37532

Open
siliu1 opened this issue Jan 6, 2025 · 3 comments
Open

Add focus-without-user-activation permissions policy #37532

siliu1 opened this issue Jan 6, 2025 · 3 comments
Labels
Content:HTTP HTTP docs waiting for implementations Waiting for feature to be implemented in browsers

Comments

@siliu1
Copy link

siliu1 commented Jan 6, 2025

MDN URL

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy

What specific section or headline is this issue about?

No response

What information was incorrect, unhelpful, or incomplete?

w3c/webappsec-permissions-policy#273 (comment). Since the issue is resolved, we should add the new permissions policy entry to MDN web doc.

What did you expect to see?

add focus-without-user-activation permissions policy on https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy.

Do you have any supporting links, references, or citations?

The spec update PR: whatwg/html#10672

Do you have anything more you want to share?

No response

@siliu1 siliu1 added the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Jan 6, 2025
@github-actions github-actions bot added the Content:HTTP HTTP docs label Jan 6, 2025
@Josh-Cena Josh-Cena added help wanted If you know something about this topic, we would love your help! and removed needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. labels Jan 7, 2025
@hamishwillee
Copy link
Collaborator

@siliu1 Thank you. Is this implemented anywhere? MDN documents things once they are implemented in browsers. Can you point to tracking issues?

@siliu1
Copy link
Author

siliu1 commented Jan 27, 2025

@hamishwillee Chromium is working on the implementation and https://issues.chromium.org/issues/371112534 is used to track the progress.

@hamishwillee hamishwillee added waiting for implementations Waiting for feature to be implemented in browsers and removed help wanted If you know something about this topic, we would love your help! labels Jan 27, 2025
@hamishwillee
Copy link
Collaborator

Thanks @siliu1 - the trigger would then be when Chromium (or some other browser) provides and implementation. I've added a label to indicate we're waiting for an implementation. If chrome pushes this in, please feel free to ping us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content:HTTP HTTP docs waiting for implementations Waiting for feature to be implemented in browsers
Projects
None yet
Development

No branches or pull requests

3 participants