MV3 extension cannot load when an empty web_accessible_resources list is in manifest.json
Categories
(WebExtensions :: General, enhancement, P2)
Tracking
(firefox114 fixed)
| Tracking | Status | |
|---|---|---|
| firefox114 | --- | fixed |
People
(Reporter: robwu, Assigned: robwu)
References
Details
(Whiteboard: [addons-jira])
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
web_accessible_resources is allowed to be an empty list in MV2 (and also in Chrome's MV3).
Firefox currently refuses to load the extension when an empty web_accessible_resources list is specified.
It even refuses to load if web_accessible_resources is specified, but matches or resources is an empty list. In bug 1809431 we updated the schema to allow an empty extension_ids list.
Chrome allows the extension to load with these set to an empty list, we should too.
|
||
Updated•2 years ago
|
|
Assignee | |
Updated•2 years ago
|
|
|
Assignee | |
Updated•2 years ago
|
|
|
Assignee | |
Comment 1•2 years ago
|
||
I found another issue - web_accessible_resources does not permit additional properties. That means that extensions with use_dynamic_url will fail to load (we haven't implemented use_dynamic_url yet, it's part of bug 1713196).
|
|
Assignee | |
Comment 2•2 years ago
|
||
-
Do not require any item in the arrays
-
Allow web_accessible_resources to have unrecognized properties instead
of refusing to load the extension. -
Fix up minor quality issues in tests.
|
|
Assignee | |
Updated•2 years ago
|
|
||
Comment 4•2 years ago
|
||
| bugherder | ||
|
|
Assignee | |
Updated•2 years ago
|
Description
•