48f7830558
It seems that the issue wasn't that zotero:// URLs can't be loaded in a content browser, but rather that the report extension was returning a channel that the content browser couldn't access. For some reason, it handled that failure by passing the URL off to the OS, which then opened a duplicate instance of Zotero. Also: - Remove ensureBrowserType() and always use <browser type="content"> in basicViewer (see b8966f) - Fix system principal being used to load extensions without `loadAsChrome` set to true if an extension with `loadAsChrome` set to true had been loaded in the past |
||
|---|---|---|
| .. | ||
| zotero-autocomplete.js | ||
| zotero-protocol-handler.js | ||
| zotero-service.js | ||