UX | Screenshot | Only works on active tab

[sm17p]

Context: Screenshot only works on the active tab; active-tab permission is granted when the user clicks the extension icon, which can cause confusion after reopening the browser.

Refined: Document the tradeoff: (1) optional <all_urls> permission vs (2) in-app education (toast, FAQ). Decide and document in this issue.

Risks of (1): User skepticism, store review, need to explain permission usage.

[sm17p]

Triage pass complete.

Proposed direction:

• Keep activeTab for trust/security and add explicit UX guidance when screenshot is unavailable.
• Consider optional elevated permission only behind a clear opt-in setting.

Research notes:

• Many extensions avoid <all_urls> by default due to install friction and review risk.
• Contextual education (toast/help text) reduces confusion with less permission overhead.

Implementation slice:

1. Detect permission state before screenshot action.
2. Show actionable message explaining why it fails and how to grant broader access.
3. Document browser-specific behavior in FAQ.

Definition of done:

• Users understand why screenshot is limited and can complete screenshot flow predictably.