zotero/chrome/content
Aurimas Vinckevicius e4dd38fc84 Fix race condition when starting in Connector mode
When starting in Connector mode (i.e. Standalone is open), Zotero first starts in Full mode, looks for Standalone, then "shuts down" and restarts in Connector mode. `Zotero.shutdown()` returns a promise which is then followed up by a `Zotero.init` call. Thus, when starting in Connector mode, Zotero initialization is asynchronous and makes it possible for `Zotero_Browser.init()` to be called before `Zotero.initialized` is true, which prevents `Zotero_Browser` from initializing. Additionally, even if `Zotero_Browser.init()` is called after Zotero is initialized in Connector mode, it is possible that `Zotero_Browser.init()` will be called _after_ the "load" event for browser.xul has already fired, so `chromeLoad` is never called. This patch ensures that both of these race conditions are taken into account.
2014-06-04 03:16:29 -05:00
..
zotero Fix race condition when starting in Connector mode 2014-06-04 03:16:29 -05:00
zotero-platform Closes #482, Include active info pane tab in tab cycle on OS X 2014-05-17 04:10:37 -04:00