Closed
Bug 1746751
Opened 3 years ago
Closed 3 years ago
Use `ChromeUtils.import` with one parameter in blocklist test code
Categories
(Toolkit :: Blocklist Implementation, task, P3)
Toolkit
Blocklist Implementation
Tracking
()
RESOLVED
FIXED
97 Branch
| Tracking | Status | |
|---|---|---|
| firefox97 | --- | fixed |
People
(Reporter: mathew.hodson, Assigned: mathew.hodson)
References
Details
Attachments
(1 file)
Passing this or null as the second argument to ChromeUtils.import(..., null) causes behaviour that we don't want now. As we look towards a new module system we need to prevent this behaviour.
|
Assignee | |
Comment 1•3 years ago
|
||
Export new BlocklistPrivate to allow tests to reach implementation
objects.
|
||
Updated•3 years ago
|
Assignee: nobody → mathew.hodson
Status: NEW → ASSIGNED
|
||
Updated•3 years ago
|
Severity: -- → S3
Priority: -- → P3
Pushed by rob@robwu.nl:
https://hg.mozilla.org/integration/autoland/rev/ff2fa4c90d9d
Use `ChromeUtils.import` with one parameter in blocklist test code. r=robwu DONTBUILD
|
||
Comment 3•3 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox97:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 97 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•