jpm built extensions are not displaying inline preferences

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
4 years ago
4 years ago

People

(Reporter: KWierso, Assigned: evold)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Created attachment 8471854 [details]
@testoptions.xpi

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
      }
  ]
}
Blocks: 1034413
(Reporter)

Comment 1

4 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: nobody → evold
Summary: In-line preferences not displaying from a jpm-built extension. → jpm built extensions are not displaying inline preferences
Depends on: 1057151
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
Resolving this in https://github.com/mozilla/jpm/pull/155
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.