It caused no message body being filled when replying to a message
or such actions. There was also a runtime warning when an empty GBytes
had been passed to WebKitGTK+, thus cover that as well.
Two issues:
a) the ATTENDEE property value is supposed to be URI, specifically
a mailto: URI for email addresses
b) when the calendar has set no user email backend property, the code
returns an empty string, which had been used as the attendee address.
This had been discovered while working on a downstream bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1515776
It could happen that the snapshot save got interrupted by other UI
code, one of them being composer close, which causes the composer's
dispose() execution, even it has more than one ref_count. The dispose()
frees the content widgets, which results in use-after-free when
the snapshot save continues its execution. The interrupt was possible
also due to several asynchronous calls being involved during the save.
This had been reported downstream at:
https://bugzilla.redhat.com/show_bug.cgi?id=1538865
Indentation gap had been added in front of every text in the indented block,
which can be wrong in cases where the text is "split" by an anchor, for example
when added by magic-links. There was used wrong indentation gap in the plain
text version too (3 in UI versus 4 spaces in plain text per level).
This had been reported downstream at:
https://bugzilla.redhat.com/show_bug.cgi?id=1538775
This is related to bug 791291, but doesn't fix it, it rather makes sure that:
a) any autosave snapshot is not overwritten with empty body of the message
b) the snapshot is not deleted after "broken" composer close
c) it's offered to recover the last snapshot (if exists) on close of the composer.
This all makes sure that users will not lose all their work, only up
to one minute of time, which is the interval of the autosave.
Make the change to use localized Fwd/Re hidden from the UI, because
it can break things in an international environment and the RFC 5256
section 7 suggests not to localize those. As this is eventually bad
option, it should not be shown in the UI (there are more interesting
options hidden in gsettings without their UI counter parts too).
Since change for bug 787002 typing numbers into for example search
entry was not possible, due to the shortcuts for labels "consuming"
the key presses. The fix is to allow labels only if the message
list is focused, when also the context menu contains the Labels.
This had been reported downstream:
https://bugzilla.redhat.com/show_bug.cgi?id=1498484
Milan Crha