The legacy install.rdf seems to tell browsers apart by id...
Firefox: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
Seamonkey: {92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}
Basilisk: ???
Thanks.
What's the id of Baslisk? Topic is solved
Moderator: Basilisk-Dev
Re: What's the id of Baslisk?
Basilisk has inherited Firefox's GUID.. Not like they will have any need for it anymore... Least as far as classical add-ons are concerned. Webextension's don't use the GUID they target "gecko" specifically.
Re: What's the id of Baslisk?
So it's impossible to tell Firefox and Basilisk apart? SeaMonkey is identified like this (in Mozilla Archive Format code):New Tobin Paradigm wrote:Basilisk has inherited Firefox's GUID.. Not like they will have any need for it anymore... Least as far as classical add-ons are concerned. Webextension's don't use the GUID they target "gecko" specifically.
Code: Select all
let isSeaMonkey = Cc["@mozilla.org/xre/app-info;1"]
.getService(Ci.nsIXULAppInfo).ID == "{92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}";
Re: What's the id of Baslisk?
You could check for the application name using the same service so something like should work:
However, I question the reason you need to maintain Firefox compatibility.. Waterfox perhaps? In any event it would also let you weed out the special case when those minor builds fall by the wayside and ESR is out of date.
Hope I have helped!
Peace.
Code: Select all
let isFirefox = Cc["@mozilla.org/xre/app-info;1"].getService(Ci.nsIXULAppInfo).ID == "{ec8030f7-c20a-464f-9b0e-13a3a9e97384}";
let isBasilisk = Cc["@mozilla.org/xre/app-info;1"].getService(Ci.nsIXULAppInfo).name == "Basilisk";
if (isFirefox == true && isBasilisk == true) {
// Basilisk special case
}
else {
// Assume Firefox or some other minor rebuild
}
Hope I have helped!
Peace.
Re: What's the id of Baslisk?
Thanks for the code and yup: Waterfox (which will keep using "Gecko"). It would be hilarious to fragment the legacy ff community even further and have 3 separate addons for Waterfox, Basilisk and Pale MoonNew Tobin Paradigm wrote:However, I question the reason you need to maintain Firefox compatibility.. Waterfox perhaps? In any event it would also let you weed out the special case when those minor builds fall by the wayside and ESR is out of date