Closed
Bug 1494232
Opened 6 years ago
Closed 4 years ago
[JEXL targeting] addonsInfo.addons does not include userDisabled addons
Categories
(Firefox :: Messaging System, defect, P3)
Firefox
Messaging System
Tracking
()
People
(Reporter: giorgos, Assigned: andreio)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
(deleted),
text/x-github-pull-request
|
Details |
addonsInfo.addons does not list user disabled addons.
STR:
- Open browser console
- ChromeUtils.defineModuleGetter(this, "ASRouterTargeting",
"resource://activity-stream/lib/ASRouterTargeting.jsm");
- ASRouterTargeting.Environment.addonsInfo.then(console.log)
- Installed but user disabled addons do not get listed
Snippets needs this information to target browsers which have addon X
- installed and enabled
- installed and disabled
Updated•6 years ago
|
Assignee: nobody → andrei.br92
Iteration: --- → 64.3 (Oct 12)
status-firefox63:
--- → wontfix
status-firefox64:
--- → affected
Priority: -- → P1
Comment 1•6 years ago
|
||
Just adding notes from chatting with ddurst about the add-ons/CFR bugs. stuart coleville also a good source for this.
Ddurst: "if it's like https://searchfox.org/mozilla-central/source/browser/components/newtab/lib/ASRouterTargeting.jsm#127, the issue could be that they're using `getActiveAddons` -- which does exactly that.
If the CFR code is like that (or if that *is* that code), it should be using `getAddonsByTypes` and looking at the addons returned from that."
Updated•6 years ago
|
Iteration: 64.3 (Oct 12) → 65.1 (Nov 2)
Updated•6 years ago
|
Iteration: 65.1 (Nov 2) → 65.2 (Nov 16)
Reporter | ||
Comment 2•6 years ago
|
||
I'm doing some Snippets 2018Q4 goals housekeeping, related to this bug.
Could you update us on the status: Will this get implemented in 64? If not, should we expect it in 65?
Flags: needinfo?(tspurway)
Comment 3•6 years ago
|
||
this will not be in 64 unless we explicitly ask for uplift, though this will land in 65
Flags: needinfo?(tspurway)
Updated•6 years ago
|
Assignee: andrei.br92 → nobody
Priority: P1 → P3
Updated•6 years ago
|
Iteration: 65.2 (Nov 16) → ---
Reporter | ||
Comment 4•6 years ago
|
||
This is still not working on 65.0b11.
The original request (bug 1431525) is now one year old. Can we get an update whether this is fixed or when will be fixed to plan accordingly?
Thanks!
Flags: needinfo?(tspurway)
Comment 5•6 years ago
|
||
i am clearing the priority field so this comes up in next week's triage
Flags: needinfo?(tspurway)
Priority: P3 → --
Comment 6•6 years ago
|
||
Updated•6 years ago
|
Iteration: --- → 67.2 - Feb 11 - 24
Priority: -- → P1
Updated•6 years ago
|
Assignee: nobody → andrei.br92
Updated•6 years ago
|
Iteration: 67.2 - Feb 11 - 24 → 68.1 - Mar 18 - 31
status-firefox65:
--- → wontfix
status-firefox66:
--- → wontfix
status-firefox67:
--- → wontfix
Priority: P1 → P2
Updated•6 years ago
|
Priority: P2 → P1
Updated•6 years ago
|
Iteration: 68.1 - Mar 18 - 31 → 68.2 - Apr 1 - 14
Updated•6 years ago
|
Iteration: 68.2 - Apr 1 - 14 → ---
Priority: P1 → P2
Updated•5 years ago
|
Component: Activity Streams: Newtab → Messaging System
Updated•4 years ago
|
Priority: P2 → P3
Updated•4 years ago
|
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•