b8966f7878
- The protocol can no longer be marked "dangerous to load," only "UI resource" (accessible inside browsers but not by web pages). - The protocol needs to run in the main process. - We need to replace the XUL browser to reset its type attribute depending on whether we're loading a zotero protocol URI - zotero protocol URIs, maybe due to the protocol handler's tight coupling with the main process, cannot load in type="content" browsers. |
||
|---|---|---|
| .. | ||
| zotero-autocomplete.js | ||
| zotero-protocol-handler.js | ||
| zotero-service.js | ||