Closed Bug 681432 Opened 13 years ago Closed 10 years ago

Fennec does not display addons with 3rd party addon types in addon manager

Categories

(Firefox for Android Graveyard :: Add-on Manager, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Firefox 37

People

(Reporter: erikvvold, Assigned: Margaret)

Details

Attachments

(1 file, 1 obsolete file)

I'm working on a branch of Scriptish for Fennec, https://github.com/erikvold/scriptish/tree/fennec , and I was hoping that the addon manager for Fennec would display 3rd party addons like the FF addon manager does =]

Is that the plan?
It displays add-ons installed from any http source, so I'm not sure which kind of issue you see here.
Hi Erik. As mentioned in Comment 1 we show installed add-ons from any http source. Please re-open this bug if you find an issue with this. If so, please let us know the details of the add-on that does NOT show in our add-on manager. Thanks!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
OK you guys clearly misunderstood what I was talking about..

In FF4 the AddonManager https://developer.mozilla.org/en/Addons/Add-on_Manager was introduced which allows third party addons to create new addons types. So extensions like Stylish and Greasemonkey can easily extend the EM with new addon types.

This does not seem possible with Fennec even though the AddonManager API seems intact..
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Summary: Fennec does not display 3rd party addons in addon manager → Fennec does not display addons with 3rd party addon types in addon manager
Since Fennec will be using a native UI, this may be more important.  Addons like Scriptish will not be able to support Fennec without this feature.
Component: Extension Compatibility → Add-on Manager
Product: Fennec Graveyard → Firefox for Android
Version: Firefox 6 → Trunk
Eric, is this still a problem? If it is, can you link to an XPI that demonstrates this problem, and elaborate on what you'd like us to do to fix this?
Flags: needinfo?(evold)
(In reply to :Margaret Leibovic from comment #5)
> Eric, is this still a problem? If it is, can you link to an XPI that
> demonstrates this problem, and elaborate on what you'd like us to do to fix
> this?

I'll have to make a new add-on for this, the old one only worked on the pre-native Fennec.

I'll get to it eventually hopefully, I'm pretty sure that Blair would know if this still works or not though.
Flags: needinfo?(bmcbride)
(In reply to Erik Vold [:erikvold] (work week -> pto) from comment #6)
> (In reply to :Margaret Leibovic from comment #5)
> > Eric, is this still a problem? If it is, can you link to an XPI that
> > demonstrates this problem, and elaborate on what you'd like us to do to fix
> > this?
> 
> I'll have to make a new add-on for this, the old one only worked on the
> pre-native Fennec.
> 
> I'll get to it eventually hopefully, I'm pretty sure that Blair would know
> if this still works or not though.

* still does not work
Flags: needinfo?(evold)
Flags: needinfo?(evold)
I don't generally touch the Fennec frontend implementation - it's completely independent from the Toolkit implementation, and maintained completely independently (for better or worse).

But I do know it's far less feature complete, and doesn't make the expected use of the provided AddonManager APIs. One such example is that it uses a hard-coded list of add-on types, rather than using AddonManager.addonTypes object and associated event handlers (the TypeListener interface). This ends up meaning that it only supports add-on types that it's hard-coded to support.
Flags: needinfo?(bmcbride)
I don't have time to look into this, I have 5+ projects that I have to work on right now, native jetpacks, jpm, add-ons as features, mochitestification & cfx test suite updates for the sdk, sdk uplifts, and various reviews across this scope.

Perhaps someone on the Fennec team can look into this?
Flags: needinfo?(evold) → needinfo?(margaret.leibovic)
Attachment #8533359 - Flags: review?(mark.finkle)
/r/1321 - Bug 681432 - Support all add-on types in the add-on manager

Pull down this commit:

hg pull review -r 2369985310ec405df277f5e97262ae1acd224c39
I wasn't able to reproduce this locally, since I don't have an example add-on that does this, but I believe this fix should be enough to fix this issue. I'm not sure why we only request certain add-on types as opposed to all add-ons. I assume this is just some historical artifact, so I think we can update this to get all add-ons.
Flags: needinfo?(margaret.leibovic)
Assignee: nobody → margaret.leibovic
https://reviewboard.mozilla.org/r/1321/#review705

::: mobile/android/chrome/content/aboutAddons.js
(Diff revision 1)
> -    AddonManager.getAddonsByTypes(["extension", "theme", "locale"], function(aAddons) {
> +    AddonManager.getAllAddons(function(aAddons) {

I suppose this is safe enough. I don't expect to see many other types appearing for Fennec, although the new "experimental" type might be something we support sometime in the future.
(In reply to Mark Finkle (:mfinkle) from comment #14)
> https://reviewboard.mozilla.org/r/1321/#review707
> 
> Ship It!

Really?
https://hg.mozilla.org/integration/fx-team/rev/c310bb6e6bc6

I guess a "ship it" in rb doesn't automatically set an r+ in the bug?
https://hg.mozilla.org/mozilla-central/rev/c310bb6e6bc6
Status: REOPENED → RESOLVED
Closed: 13 years ago10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 37
Comment on attachment 8533359 [details]
MozReview Request: bz://681432/margaret

(The r+ happened in review board)
Attachment #8533359 - Flags: review?(mark.finkle) → review+
Attachment #8533359 - Attachment is obsolete: true
Attachment #8617982 - Flags: review+
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: