Closed
Bug 1464711
Opened 5 years ago
Closed 4 years ago
Typo in ExtensionContent Script.requiresCleanup()
Categories
(WebExtensions :: General, enhancement, P1)
Tracking
(firefox66 fixed)
RESOLVED
FIXED
mozilla66
Tracking | Status | |
---|---|---|
firefox66 | --- | fixed |
People
(Reporter: zombie, Assigned: rpl)
Details
(Whiteboard: typescript-check)
Attachments
(1 file)
Typescript check found that property removeCss doesn't exist: https://searchfox.org/mozilla-central/rev/5a74471/toolkit/components/extensions/ExtensionContent.jsm#306
Updated•5 years ago
|
Product: Toolkit → WebExtensions
Comment 1•5 years ago
|
||
Hello, I'm an absolute beginner and would like to work on it.
Comment 2•5 years ago
|
||
Devika, thanks for your interest! Unfortunately, I don't think this is a particularly good first bug. In particular, removeCss looks like a mis-capitalization of removeCSS so it should probably be changed. But the fact that everything is working with that typo in place suggests we don't have very good test coverage here so ideally we would improve the test coverage at the same time. If you're interested in looking into that, feel free but since you say you're an absolute beginner, I would encourage you to look at bugs with the good-first-bug keyword.
Updated•4 years ago
|
Assignee: nobody → lgreco
Priority: -- → P1
Assignee | ||
Comment 3•4 years ago
|
||
This patch fixes the typo in the requiresCleanup getter and adds an additional step
in the automated tests to verify that the scripts created by browser.tabs.removeCSS
are not being added to the content scripts that requires cleanup.
Pushed by luca.greco@alcacoop.it: https://hg.mozilla.org/integration/autoland/rev/ca8f8514f60d Fix typo in ExtensionContent script.requiresCleanup getter. r=zombie
Comment 5•4 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox66:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
Assignee | ||
Comment 6•4 years ago
|
||
Setting qe-verify-, as this is tested in automation.
Flags: qe-verify-
Updated•4 years ago
|
status-firefox62:
affected → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•