Closed
Bug 721298
Opened 14 years ago
Closed 14 years ago
Fennec XUL has no suggested addons
Categories
(addons.mozilla.org Graveyard :: Administration, defect)
addons.mozilla.org Graveyard
Administration
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kbrosnan, Assigned: mbrubeck)
Details
Opening the nightly XUL Fennec 11a2 build has no suggested addons on the about:home screen. The about:addons screen has no suggested addons either. Doing a search on the site for phony or other mobile addons are set to 11a1.
We will be distributing the XUL version for tablet users. These users should still be able to find addons via AMO.
Updated•14 years ago
|
tracking-fennec: ? → 11+
Comment 1•14 years ago
|
||
Where do the suggested add-ons on the about:home screen come from?
Updated•14 years ago
|
Keywords: fennecnative-betablocker
| Reporter | ||
Comment 2•14 years ago
|
||
These are the recommended addons. https://addons.mozilla.org/en-US/mobile/extensions/?sort=featured The problem from what I can see is that there are no 11a2 compatible extensions. Should we be chasing the addon devs to bump their extensions?
| Assignee | ||
Comment 3•14 years ago
|
||
AMO has not yet been updated with any Fennec versions beyond 11.0a1, so add-on develpers can't bump the compatibility yet. I think Mark Finkle has access to add new versions; if not, we can move this bug to AMO.
Comment 4•14 years ago
|
||
To match Firefox Desktop, I added: 11.0a2, 11.0, 11.* and 12.0a1
| Assignee | ||
Comment 5•14 years ago
|
||
I've updated several of my add-ons to be compatible with Aurora and Nightly.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•14 years ago
|
Assignee: nobody → mbrubeck
status-firefox11:
--- → fixed
Updated•14 years ago
|
blocking-fennec1.0: --- → beta+
| Assignee | ||
Comment 6•14 years ago
|
||
Not a native Fennec bug; removing it from the blocker list.
blocking-fennec1.0: beta+ → -
Updated•10 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•