Closed
Bug 1451795
Opened 7 years ago
Closed 7 years ago
Store the devtools pages definitions into the instance of the ExtensionAPI class instead of a global Map.
Categories
(WebExtensions :: Developer Tools, enhancement, P3)
Tracking
(firefox62 fixed)
RESOLVED
FIXED
mozilla62
Tracking | Status | |
---|---|---|
firefox62 | --- | fixed |
People
(Reporter: rpl, Assigned: rpl)
References
Details
Attachments
(1 file)
This is a follow up originated from Bug 1394750 review comments:
::: browser/components/extensions/ext-devtools.js:483
(Diff revision 4)
> +
> // Create and register a new devtools_page definition as specified in the
> // "devtools_page" property in the extension manifest.
> - let devtoolsPageDefinition = new DevToolsPageDefinition(extension, manifest.devtools_page);
> + let devtoolsPageDefinition = new DevToolsPageDefinition(extension, manifest.devtools_page,
> + () => this.isDevToolsDisabled());
> devtoolsPageDefinitionMap.set(extension, devtoolsPageDefinition);
>> It doesn't have to happen here, but can we just store this
>> in the instance of the API class rather than in a global Map?
>Yeah, I think that we can do that if we also change the way we lazily
>initialize the devtools API (which is currently happening when we create
>the first devtools page definition from a devtools_page manifest entry,
>from the global initDevTools function which is accessing that map:
https://searchfox.org/mozilla-central/rev/f5fb323246bf22a3a3b4185882a1c5d8a2c02996/browser/components/extensions/parent/ext-devtools.js#293)
(quoted from https://bugzilla.mozilla.org/show_bug.cgi?id=1394750#c36)
Assignee | ||
Updated•7 years ago
|
Comment hidden (mozreview-request) |
Comment hidden (mozreview-request) |
Comment hidden (mozreview-request) |
Assignee | ||
Updated•7 years ago
|
Attachment #8969733 -
Flags: review?(aswan)
Comment 4•7 years ago
|
||
mozreview-review |
Comment on attachment 8969733 [details]
Bug 1451795 - Move lazy devtools initialization helper into a static method of the ExtensionAPI.
https://reviewboard.mozilla.org/r/238544/#review246742
This looks great!
::: browser/components/extensions/parent/ext-devtools.js:320
(Diff revision 3)
> -// Get the devtools preference given the extension id.
> -function getDevToolsPrefBranchName(extensionId) {
> - return `devtools.webextensions.${extensionId}`;
> +this.devtools = class extends ExtensionAPI {
> + constructor(extension) {
> + super(extension);
> +
> + // DevToolsPageDefinition instance (created in onManifestEntry).
> + this.devtoolsPageDefinition = null;
nit: Since you're inside the devtools api, I think it would be clear to just call this something like pageDefinition and everything would be a little more concise. This is a matter of taste though, feel free to leave it if you prefer it as is.
Attachment #8969733 -
Flags: review?(aswan) → review+
Comment hidden (mozreview-request) |
Comment hidden (mozreview-request) |
Assignee | ||
Comment 7•7 years ago
|
||
(In reply to Andrew Swan [:aswan] from comment #4)
> nit: Since you're inside the devtools api, I think it would be clear to just
> call this something like pageDefinition and everything would be a little
> more concise. This is a matter of taste though, feel free to leave it if
> you prefer it as is.
Actually, I totally agree.
Change applied (and patch rebased on a recent mozilla-central tip).
Pushed by luca.greco@alcacoop.it:
https://hg.mozilla.org/integration/autoland/rev/6e55646aad4a
Move lazy devtools initialization helper into a static method of the ExtensionAPI. r=aswan
Comment 9•7 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox62:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
Updated•7 years ago
|
Flags: qe-verify-
Updated•7 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•