Closed
Bug 1052803
Opened 12 years ago
Closed 12 years ago
jpm built extensions are not displaying inline preferences
Categories
(Add-on SDK Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: KWierso, Assigned: evold)
References
Details
Attachments
(1 file)
|
5.85 KB,
application/x-xpinstall
|
Details |
Splitting this part off of bug 1038003, as that also covers Android's in-line options, even with the cfx tool...
I'm trying to transition one of my extensions from cfx to jpm, but I noticed that the extension's in-line preferences aren't being displayed in the Add-on Manager. I don't even see the "Options" button for the extension's AOM entry.
I'm using the current tip of jpm's master branch, against today's Windows Nightly build. I haven't tested on OSX or Linux, so I don't know if this is platform specific or not.
Attached is a really simplified extension that reproduces the issue.
The extension's package.json contents are as follows:
{
"title": "Test Options",
"name": "testoptions",
"version": "0.0.0",
"description": "Test In-Line Options",
"main": "index.js",
"author": "KWierso",
"engines": {
"firefox": ">=33.0a1"
},
"license": "MIT",
"preferences": [
{
"name": "boolOptions",
"title": "Test boolean options",
"type": "bool",
"value": true
}
]
}
| Reporter | ||
Comment 1•12 years ago
|
||
The preferences do seem to exist in about:config, so it appears to be creating the preferences, just not showing them to the addon manager.
| Assignee | ||
Updated•12 years ago
|
Assignee: nobody → evold
Summary: In-line preferences not displaying from a jpm-built extension. → jpm built extensions are not displaying inline preferences
| Assignee | ||
Comment 2•12 years ago
|
||
There is nothing that we should do on the sdk side for this, I have a patch for jpm here https://github.com/mozilla/jpm/pull/155
| Assignee | ||
Comment 3•12 years ago
|
||
Resolving this in https://github.com/mozilla/jpm/pull/155
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
| Assignee | ||
Comment 4•12 years ago
|
||
This should work now, as of https://github.com/erikvold/jpm/commit/74d6c6c9dfaad4b3dff3951ad4b171765d3c1747
You need to log in
before you can comment on or make changes to this bug.
Description
•