| Age | Commit message (Collapse) | Author |
|---|
|
SMTP json is a blocking HTTP request that was taking ~1 sec
of the session creation. We moved it to the UA initialization
|
|
|
|
|
|
In some cases, the default home was not expanding
the user part of the path and was causing errors,
now we make sure the path is expanded when setting
the default value
|
|
Soledad json must only be downloaded after we
fetch the api provider certificate, we can't
make the request for it before having this cert
|
|
See: #761
|
|
|
|
|
|
|
|
|
|
|
|
Now we can clock how long a piece of code takes
to execute without being constrained by whole
method like we were with the decorator
|
|
The README explains how to apply the patch so you
can get information about long running methods (longer
than 100ms) on the main thread
|
|
Started adapting get_leap_session to deferreds
Soledad and keymanager setup calls will now
happen in deferreds and leap session creation
itself is a deferred with callbacks
This is a start in breaking the big blocking
calls we were doing on the main thread, this
was done without changing code inside the
leap libraries yet so things can be further
optimized
This breaks the ~4 seconds get_leap_session
piece into smaller 1 seconds one, that can be
further optimized and deferred to even smaller
calls
There are requests calls happening on the main
thread that should get this number even further
down
Also moved some pieces from bitmask libraries
to our bootstrap, because they are not bitmask
libraries anymore and that was causing confusion
|
|
Authentication is now consistently done before
creating the leap session, so I removed the
auth attempt from inside the leap session
factory
|
|
Consolidated authentication to always be
done is a defer to thread and changed the
authenticate_user method name to conform
with what it actually does
|
|
It is already done earlier in the bootstrap and
is not user specific, so shouldn't be done on
user bootstrap
|
|
Reason for the failure: see
https://github.com/karma-runner/karma-phantomjs-launcher/issues/104
|
|
See #751
|
|
at least phantomjs-prebuilt has issues if the node_modules
dir is a symbolic link. Which is the case inside vagrant.
See #751
|
|
The encryption status was being wrongly displayed as
"encrypted encryption-valid" with a green padlock
See: #619
|
|
|
|
Compose now is a HTML Button
|
|
Changing icon size and margin
|
|
So far the mail item had some padding applied to it on all sides,
inside this padding area the item was not clickable, even though
the cursor changed to a pointer. By moving the padding into the
<a> tag, the whole element becomes clickable and opens the email.
fixes #743
|
|
Make whole mail item without tags clickable
|
|
Great! Thanks a lot.
|
|
|
|
fixes #743
For mail items without tags the link to open the mail is not expanded,
therefore it has to be done via CSS
|
|
|
|
|
|
|
|
|
|
|
|
This change is based on official node instructions.
|
|
exchanged paper-plane icon for sent icon, fixes #717
|
|
|
|
|
|
We have some tests running around 600 ms.
We changed the report value for slower tests
to 1 sec.
This eliminates the last warnings on js tests.
|
|
We added a proxy to serve the sandbox.html.
This removes warnings from js tests
|
|
|
|
We had some tests trying to hit the backend.
Considering these are unit tests, we decided
to mock all ajax calls.
This removes the warnings we had when running
js tests.
|
|
See: #727
|
|
|
|
|
|
This reverts commit dd1c1ee473364e2b298ee4fbdf11abc2894932d8.
|
|
|
|
|
|
|
|
|
