Closed Bug 1745822 Opened 4 years ago Closed 2 years ago

Implement MV3 optional_host_permissions

Categories

(WebExtensions :: General, enhancement, P3)

enhancement
Points:
8

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1766026

People

(Reporter: zombie, Unassigned)

References

(Blocks 1 open bug)

Details

  • ⬜ At every “passive” place where host permissions/match patterns are checked for the current active tab, send a message to the parent process to flag the browser action button, to inform users that extension wants access:
    • Content script match patterns
    • webRequest events
    • Tab events
    • Cookie events
    • Basically every event that checks host permission before firing.
  • ⬜ Keep track of sites where user was already notified, and where they declined.
  • ⬜ Have a limited number of times we would notify per site.
  • ⬜ Have a global limit for each extension.
Points: --- → 8
Severity: -- → N/A
Priority: -- → P2
Depends on: 1777343
Priority: P2 → P3

The wishlist idea has evolved in the WECG into optional_host_permissions. This issue is about implementing the WECG definition.

Summary: Implement Wishlist permissions → Implement MV3 optional_host_permissions
Status: NEW → RESOLVED
Closed: 2 years ago
Duplicate of bug: 1766026
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.