Open
Bug 1480276
Opened 6 years ago
Updated 2 years ago
Find a way for browser_all_files_referenced.js to get dynamic chrome/resource registrations
Categories
(Firefox :: General, enhancement, P3)
Firefox
General
Tracking
()
NEW
People
(Reporter: aswan, Unassigned)
Details
browser_all_files_referenced.js currently iterates over the contents of an app dir and: 1. parses all the manifest files it can find to work out where files are accessible via chrome: and resource: urls 2. uses the results of step 1 to map all the source files it can find back to chrome/resource urls to produce the initial list of "all files present in the build" This (sort of) works for bootstrapped extensions since they still specify chrome and resource registrations in chrome.manifest files. As we move to webextensions with bundled apis, these registrations move to dynamic code, as in: https://searchfox.org/mozilla-central/rev/d0a0ae30d534dc55e712bd3eedc1b4553ba56323/testing/mochitest/api.js#111-117 (the mochitest extension is ignored for the purposes of this test, but it illustrates how webextension system add-ons that need to register chrome/resource substitutions work) An expedient solution is to hard-code chrome/resource prefixes registered by system addons in the test (and this is what I plan to do for the time being in bug 1449055). This bug is to consider/discuss adding a method for the test to get these mappings directly from the chrome registry and the resource protocol handler.
Updated•5 years ago
|
Component: General → Untriaged
Product: Firefox → WebExtensions
Reporter | ||
Comment 2•5 years ago
|
||
I'm not sure why this was moved, this bug is about improvements to a general Firefox unit test, not about changing anything in the webextensions framework.
Component: Untriaged → General
Product: WebExtensions → Firefox
Comment 3•5 years ago
|
||
(In reply to Andrew Swan [:aswan] from comment #2)
I'm not sure why this was moved, this bug is about improvements to a general Firefox unit test, not about changing anything in the webextensions framework.
Likely because the first comment contains a lot of mentions to extensions, webextensions, addons.
The bot is using machine learning to assign a component, so it can't be perfect.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•