It can be trivially exploited online, so no service page should be
using this. I'll gladly help people report bugs upstream if It
comes down to that, but electron strongly recommends this.
We don't actually use any of the app.quit hooks,
this solves an additional problem with occasional
on-exit hangs with Windows as well.
Also included: tray menu finally uses locale.
This still has the same issues with actually removing old data as
upstream. Electron issues and other requests have gone unanswered, so
pushing to master.
This took some doing, but fixed the service removal thanks to ES6
Promises and a lot of detective work.
Also removed Auth0, and replaced it with a human-readable JSON
exporter/importer that works in the same way.
Just make the checkboxes uneditable until after the service is
actually created. I consider this a bad usability issue, but
am having trouble getting ExtJS to allow any access to the
necessary information while a service is being created.
commit.
NOTE: If you query window.setTimeout for timer granularity, or
EventTarget.prototype.addEventListener for passive listeners,
for a particular ap in the dev console and it says 'native code',
it's disabled.
The upstream build script was running a full npm install instead of
taking advantage of electron-builder. This should prevent unnecessary
package recalculation for both regular node packages and recompilation
of native dependencies.
rimraf was in normal dependencies, but without squirrel can live in
devDependencies instead.
This should decently speed up all forms of package building.
it and none of the apps should be using plugins.
If I'm wrong, let me know. Eg, I can call using Hangouts/GMail without
it.
Mobile webview support requires browser plugins to be disabled anyway.
TheGoddessInari
Tim Brust