Closed
Bug 1811230
Opened 2 years ago
Closed 2 years ago
Consider extension storage inspection always enabled
Categories
(DevTools :: Storage Inspector, task)
DevTools
Storage Inspector
Tracking
(firefox111 fixed)
RESOLVED
FIXED
111 Branch
Tracking | Status | |
---|---|---|
firefox111 | --- | fixed |
People
(Reporter: ochameau, Assigned: ochameau)
References
Details
Attachments
(2 files)
devtools.storage.extensionStorage.enabled preference has been enabled for a while on all channels and can be dropped.
Assignee | ||
Comment 1•2 years ago
|
||
This pref has been true for a while and isn't meant to be disabled by the user.
Updated•2 years ago
|
Assignee: nobody → poirot.alex
Status: NEW → ASSIGNED
Pushed by apoirot@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5f48bf683639
[devtools] Consider extension storage inspection always enabled. r=devtools-reviewers,nchevobbe
Comment 3•2 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox111:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
Comment 4•2 years ago
|
||
@Alexandre: Your patch re-added extensions.unifiedExtensions.enabled to firefox.js - that was removed in bug 1799009 and is no longer used.
Flags: needinfo?(poirot.alex)
Assignee | ||
Comment 5•2 years ago
|
||
Assignee | ||
Comment 6•2 years ago
|
||
Thanks for catching that and sorry for the delay.
Assignee | ||
Updated•2 years ago
|
Flags: needinfo?(poirot.alex)
Pushed by apoirot@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ccc9339f3ec9
[devtools] Re-remove extensions.unifiedExtensions.enabled which was reintroduced by mistake. r=rpl
Comment 8•2 years ago
|
||
bugherder |
Comment 9•2 years ago
|
||
A patch has been attached on this bug, which was already closed. Filing a separate bug will ensure better tracking. If this was not by mistake and further action is needed, please alert the appropriate party. (Or: if the patch doesn't change behavior -- e.g. landing a test case, or fixing a typo -- then feel free to disregard this message)
You need to log in
before you can comment on or make changes to this bug.
Description
•