Closed
Bug 1745822
Opened 4 years ago
Closed 2 years ago
Implement MV3 optional_host_permissions
Categories
(WebExtensions :: General, enhancement, P3)
WebExtensions
General
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.
Updated•4 years ago
|
| Reporter | ||
Updated•4 years ago
|
Points: --- → 8
| Reporter | ||
Updated•4 years ago
|
Severity: -- → N/A
Priority: -- → P2
Updated•2 years ago
|
Priority: P2 → P3
Comment 1•2 years ago
|
||
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
Updated•2 years ago
|
Updated•2 years ago
|
Whiteboard: [mv3-m2]
You need to log in
before you can comment on or make changes to this bug.
Description
•