A runtime warning like this:
evolution-mail-WARNING **: Failed to find parent <object>
for '.message.mixed.1.mbox.0.rfc822.attachment-bar' - no ID set?
could be shown when a message in the preview had a message attachment,
which had also an attachment.
The reason for it was a use of the same variable name in the 'for' body
as in the parent block, which, even the element was found, didn't set
the parent block's variable, thus it behaved like nothing was found.
The problem is that if we call webkit_dom_event_target_add_event_listener
on the element and unref it afterwards (even when we get that element
from WebKitDOMNodeList) the callback won't be called at all.
The crash happened when there was an attempt to connect securely
to the server, but the server provided untrusted certificate,
thus Evolution wanted to ask for the certificate trust.
Allow the atk implementation for ECellToggle to expose names for
states, since an ECellToggle can potentially show many states,
so setting ATK_STATE_CHECKABLE isn't always sufficient. Also
expose the corresponding enum of the icon through AtkValue, in case
an AT wants to perform a custom action for a particular value. Use
this functionality for the "status" cells in the message list.
It wasn't checked whether the passed-in URI was correct, but the message
object returned from soup_message_new() was dereferenced anyway, which
could cause a crash.
Follow-up fix that fixes the leak of two strings introduced with
previous fix to this bug. Also unref all the used objects from various
lists that WebKit returns after they are used.
A 4-pixel wide border looked fine for single emails, but once
the message was part of a conversation, with quoted replies,
the wider border was confusing, too close to the quotation line.
This change moves the wider border to the opposite side.
Just to make sure that all data had been written, while the later
can finish successfully without actually write all the data it was
requested to write.
Since this change the client is responsible to provide credentials
to use to authenticate backends (through ESource-s, to be more precise),
unless the credentials are already saved.
A simple Evolution run and move between all views means creation of
more than 100 GSettings objects, with only a bit more than 10 schemas.
Reusing the objects should have a positive impact on a performance too.
This reverts commit 7c918831a8.
It turned out that the Evolution won't quit when the quit was initiated
with a "busy" EShellBackend. In that case the EShellBackend itself
references the activity and lets it alive until the activity is completed.
The problem is that the activity is completed only after it is freed,
thus there happens a circular dependency on the reference count of
that activity.
We have to finish the async task before we continue with saving (that
code was unintentionally removed when merging the WebKit based composer
into the master).
