Closed
Bug 1149221
Opened 10 years ago
Closed 10 years ago
Disabled simulator still appear in WebIDE runtime list
Categories
(DevTools Graveyard :: WebIDE, defect)
DevTools Graveyard
WebIDE
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jryans, Assigned: janx)
References
Details
(Keywords: regression)
After bug 1090949 (I think), disabling a simulator from the Add-on Manager page leaves it in the WebIDE runtime list forever. Effectively, disabling has no effect.
I believe this is because WebIDE now searches out simulators by regex, effectively ignoring the add-on manager's info, since it now only needs file locations on disk and does not care about code the add-on would have run.
STR:
1. Open WebIDE
2. Look at runtime list
3. Open about:addons
4. Disable some simulator add-on
5. It will still be displayed in the runtime list
Reporter | ||
Comment 1•10 years ago
|
||
Jan, I marked this as a regression mostly for tracking purposes. I could imagine an argument that we don't care about this and decide to do nothing. However, if it's easy to fix, we may want to do, as it's a little surprising.
Assigning and setting ni? since you'll be out a few days.
Assignee: nobody → janx
Blocks: simulator-configuration
Status: NEW → ASSIGNED
Flags: needinfo?(janx)
Keywords: regression
Assignee | ||
Comment 2•10 years ago
|
||
Nice catch. Like for bug 1149214, this happens because the list is currently generated directly from what `AddonManager.getAllAddons()` returns, including disabled addons.
This will be fixed when bug 1090949's last patches get merged, because they improve the way this list is updated.
Reporter | ||
Comment 4•10 years ago
|
||
(In reply to Jan Keromnes [:janx] from comment #3)
> Does this problem still occur?
No, it seems to be fixed now, thanks!
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Flags: needinfo?(jryans)
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Firefox → DevTools
Updated•5 years ago
|
Product: DevTools → DevTools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•