Closed
Bug 840549
Opened 11 years ago
Closed 11 years ago
supporting Addon-sdk addons across multiple firefox versions
Categories
(Add-on SDK Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: glind, Unassigned)
Details
Addon-sdk is getting to be a stable, real project. This means that addons might need to last "across versions", and code bases might need to support multiple versions. Case in point: per-window private browsing. My addon needs to support 18, 19, 20, and privacy mode in all of them. I don't want to use the version number for splitting the code base. I would prefer to use some sort of duck-typing to check for existence. (My particular issue... is PB.isActice 'real' or not?). Some suggestions: 1. `utils/deprecate.js:deprecateFunction` could add a __deprecated attribute? 2. simplify down the version comparator stuff? 3. deprecateFunction(myfun).name === "deprecated" <- yuck!
Flags: needinfo?(dtownsend+bugmail)
Comment 1•11 years ago
|
||
(In reply to Gregg Lind (User Research - Test Pilot) from comment #0) > Addon-sdk is getting to be a stable, real project. > > This means that addons might need to last "across versions", and code bases > might need to support multiple versions. > > Case in point: per-window private browsing. > > My addon needs to support 18, 19, 20, and privacy mode in all of them. I > don't want to use the version number for splitting the code base. I would > prefer to use some sort of duck-typing to check for existence. (My > particular issue... is PB.isActice 'real' or not?). Why don't you want to use version checks here? They should be the most general way to do this.
Flags: needinfo?(dtownsend+bugmail)
Flags: needinfo?(glind)
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(glind)
Resolution: --- → WONTFIX
Reporter | ||
Comment 2•11 years ago
|
||
I have since moved to a 'volo add' vision for micropilot. I don't really like having to include old versions of indexed-db in order to support old Fx, but that is life :)
You need to log in
before you can comment on or make changes to this bug.
Description
•