Closed
Bug 745857
Opened 12 years ago
Closed 7 years ago
Need a way to set the optionsURL to a chrome window (or anything else)
Categories
(Add-on SDK Graveyard :: General, enhancement, P4)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: erikvvold, Unassigned)
References
Details
This is something that any traditional add-on could do easily, and it should be easy to do with the add-on sdk as well.
What would be the use case for this?
Whiteboard: [triage:followup]
Updated•12 years ago
|
Assignee: erikvvold → evold
Updated•12 years ago
|
Severity: normal → enhancement
Priority: -- → P4
Whiteboard: [triage:followup]
Updated•11 years ago
|
Comment 2•11 years ago
|
||
bug 559306 would resolve this.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
This ticket was marked as a duplicate of 559306, but that is not true. optionsURL is specified in install.rdf and not chrome.manifest. So there is still no way to specify optionsURL (and optionsType).
Updated•11 years ago
|
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Updated•11 years ago
|
Blocks: native-jetpack
Comment 4•11 years ago
|
||
If we want to do this, then I have basically done it while working on bug 915376 already, but I think we might want to use a preference instead here in order to avoid package.json bloat. Irkali thoughts?
Flags: needinfo?(rFobic)
Comment 5•11 years ago
|
||
Erik we talked about this during weekly, so yes it looks like we should provide a way to expose `optionsURL`. That being said I'm not sure what do you mean by using preference instead, can you elaborate please ? Some example may help as well.
Flags: needinfo?(rFobic)
Updated•10 years ago
|
Flags: needinfo?(evold)
Comment 6•10 years ago
|
||
(In reply to Irakli Gozalishvili [:irakli] [:gozala] [@gozala] from comment #5) > Erik we talked about this during weekly, so yes it looks like we should > provide a way to expose `optionsURL`. > > That being said I'm not sure what do you mean by using preference instead, > can you elaborate please ? Some example may help as well. At the moment the AOM determines the optionsURL from a value in the install.rdf only. I'm suggesting that there could be a fallback check for a optionsURL in say `'extensions.' + id + '.optionsURL'` for example, which would be provided by the `package.json` like so: { ... "preferences": [{ "name": "optionsURL", "type": "hidden" "value": "chrome://.." }] ... }
Flags: needinfo?(evold)
Updated•10 years ago
|
No longer blocks: native-jetpack
Depends on: native-jetpack
Comment 7•10 years ago
|
||
I'm not working on this at the moment, and it probably doesn't make sense to work on this until bug 915376 is complete.
Updated•10 years ago
|
Assignee: evold → nobody
Comment 8•7 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1399562
Status: REOPENED → RESOLVED
Closed: 11 years ago → 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•