Hackish way of avoiding async AddonManager APIs during initialization
This commit is contained in:
parent
3eef17578d
commit
15c79766e8
2 changed files with 3 additions and 2 deletions
|
@ -1,5 +1,6 @@
|
|||
content zotero chrome/content/zotero/
|
||||
content zotero-platform chrome/content/zotero-platform/ platform
|
||||
content zotero-resource resource/
|
||||
|
||||
locale zotero en-US chrome/locale/en-US/zotero/
|
||||
locale zotero af-ZA chrome/locale/af-ZA/zotero/
|
||||
|
|
|
@ -797,9 +797,9 @@ if(appInfo.platformVersion[0] >= 2) {
|
|||
.getService(Components.interfaces.nsIChromeRegistry);
|
||||
var ioService = Components.classes["@mozilla.org/network/io-service;1"]
|
||||
.getService(Components.interfaces.nsIIOService);
|
||||
var zoteroURI = ioService.newURI("chrome://zotero/content/", "UTF-8", null);
|
||||
var zoteroURI = ioService.newURI("chrome://zotero-resource/content/", "UTF-8", null);
|
||||
zoteroURI = cr.convertChromeURL(zoteroURI).QueryInterface(Components.interfaces.nsIFileURL);
|
||||
return zoteroURI.file.parent.parent.parent.parent;
|
||||
return zoteroURI.file.parent.parent;
|
||||
}
|
||||
|
||||
function getDefaultProfile(prefDir) {
|
||||
|
|
Loading…
Reference in a new issue