Writing to the pipe from Firefox was sometimes taking 100 ms for me when
opening Standalone, which meant that Zotero for Firefox would display an
error until Firefox was restarted.
And close DB on incompatible version error
This should make things a bit smoother for people upgrading to 5.0
before Zotero for Firefox is updated to the connector.
This is the default, but it looks like Mozilla may start enabling e10s for
extensions that don't explicitly set this to false at some point [1] before
they turn it on in all cases.
[1] https://wiki.mozilla.org/Electrolysis#Add-ons_Schedule
Calling getTransferData('zotero/item') when handling the
application/x-moz-file-promise seems to have stopped working between Fx46 and
Fx47, though I can't get older Nightly builds to run with mozregression
(Sierra?) to find the specific change. Instead, work around this by passing an
array of item ids to the file drag data provider.
Since the names of the tinderbox builds apparently aren't reliable (e.g., the latest mozilla-release-linux64-add-on-devel and mozilla-beta-linux64-add-on-devel builds are both Firefox 49)
In translation-server, the test timeout is overridden to 30 seconds, which was
also the deferred test delay, so there was a race condition that could cause
deferred tests to fail. This sets the deferred delay to 20 seconds.
For some reason, in the Fx48 translation-server, the processor passed to
processDocuments() calls in translators can't access document properties
even when they're on the same domain or even the same document. To get
around that, rewrap them for the sandbox, but there might be a better
fix here.
Addresses https://github.com/zotero/translation-server/issues/36
A few sites (e.g., Gallica) were causing alerts to pop up in Standalone during
testing, which breaks testing, so accept them automatically. (Hopefully these
don't happen during manual translation...?)
