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

Clarify ambiguous statements in permissions.contains() #38130

Open
rebloor opened this issue Feb 12, 2025 · 0 comments · May be fixed by #38154
Open

Clarify ambiguous statements in permissions.contains() #38130

rebloor opened this issue Feb 12, 2025 · 0 comments · May be fixed by #38154
Labels
Content:WebExt WebExtensions docs

Comments

@rebloor
Copy link
Contributor

rebloor commented Feb 12, 2025

MDN URL

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/permissions/contains

What specific section or headline is this issue about?

No response

What information was incorrect, unhelpful, or incomplete?

The statement "The promise is fulfilled with true only if all the extension currently has all the given permissions." is unclear.

What did you expect to see?

A clear statement of behavior.

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

No response

Do you have anything more you want to share?

No response

@rebloor rebloor added the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Feb 12, 2025
@rebloor rebloor changed the title Clarify ambiguous statements inClarify ambiguous statements in permissions.contains() Clarify ambiguous statements in permissions.contains() Feb 12, 2025
@github-actions github-actions bot added the Content:WebExt WebExtensions docs label Feb 12, 2025
@Josh-Cena Josh-Cena removed the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content:WebExt WebExtensions docs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants