Closed
Bug 1218472
Opened 9 years ago
Closed 9 years ago
Implement options API for open extension API
Categories
(WebExtensions :: Untriaged, defect)
WebExtensions
Untriaged
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: anaran, Unassigned)
Details
(Whiteboard: triaged)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:44.0) Gecko/20100101 Firefox/44.0
Build ID: 20151018052213
Steps to reproduce:
Try to implement something similar to
https://developer.mozilla.org/en-US/Add-ons/SDK/High-Level_APIs/simple-prefs
for some add-ons of mine.
E.g.
Actual results:
There seems to be no way ATM.
storage only supports local, while simple-prefs get synced (except for Android).
The is no options support in manifest, or UI (generic options pages).
Expected results:
I think it is important to have an equivalent for
https://developer.mozilla.org/en-US/Add-ons/SDK/High-Level_APIs/simple-prefs
in webextensions, else developers cannot port jetpack add-ons, even if they want to.
Reporter | ||
Updated•9 years ago
|
Flags: blocking-webextensions?(amckay)
Reporter | ||
Comment 1•9 years ago
|
||
This might already be covered by the dependencies of Bug 1208765.
Comment 2•9 years ago
|
||
Agree that this should be done, but being able to port from SDK to WebExtensions isn't necessarily a blocker for 1.0. We'll get to this later.
Flags: blocking-webextensions?(amckay) → blocking-webextensions-
Updated•9 years ago
|
Whiteboard: triaged
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Reporter | ||
Comment 3•9 years ago
|
||
WONTFIX does not sound like you intend to get to this. Why not leave it open?
Comment 4•9 years ago
|
||
I think the plan is to implement options v2 as per bug 1250784, not this one.
Updated•6 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•