الأذونات الاختيارية والطلبات أثناء التشغيل

Requesting many permissions at install time scares users and slows store review. The principle of least privilege says request only what you need, when you need it.

Optional permissions let you ask at runtime, in context.

The manifest separates permissions (granted at install) from optional_permissions (requested later). Move anything non-essential into optional.

Site access can also be optional. Declare it under optional_host_permissions so users grant access to specific sites only when they choose.

Call permissions.request in response to a user gesture, such as a button click. The browser shows a prompt.

The request prompt only appears if triggered by a direct user action. Calling it on startup or from a timer will silently fail.

Wire it to a click handler.

Before calling an API, check whether the permission is currently granted with permissions.contains.

Let users revoke access they no longer want with permissions.remove. This shrinks your attack surface.

Listen for onAdded and onRemoved to enable or disable features as permissions change.

Explain why you need a permission before prompting. A short sentence and a clear button earns far more grants than a surprise system dialog.

Extensions with broad install-time permissions face deeper review. Moving sensitive scopes to optional often speeds approval and reduces warning banners.

Always handle the case where a permission is denied. Disable or hide the feature rather than throwing errors, so the rest of the extension keeps working.

Test your optional permissions knowledge.

You learned runtime permission requests:

• Split required and optional_permissions
• Request from a user gesture with permissions.request
• Check with contains, revoke with remove
• React to onAdded and onRemoved
• Degrade gracefully when denied

Least-privilege design builds trust and eases store review.