if the value part is missing,
it otherwise crashes when calling MailtoUtil.getText()
and the exception is not handled there (it is not in at least one case).
therefore, just catch the exception in this cornercase (same for bad encoding)
and return an empty string.
QrShowFragment is used by some menu entries
available also when the fragment is not displayed;
therefore, creation on displaying is too late.
(the crash is present only on some android versions,
as many android versions seem to create "neighboured tabs" anyways -
so there should also not be much performance loss)
- say in the timespans explicitly that it is _latest after fetch_;
this matches better to server-side settings on chatmail -
but also when you have different (non-dc)-clients with different settings.
- do not show the alarming confirmation dialog for chatmail -
other, non-dc clients is usually not fitting,
and also there is anyways an auto-deletion
- the default for chatmail becomes 'automatic',
'never' is just wrong for chatmail
the string is deprecated and also no longer used on desktop/iOS.
the 'empty state view' where the string could appear
is anyways not shown often
(usually, there is 'saved messages' and 'device messages'),
so it also does not make sense to think over a replacement.
before, "Info" and "Message Details" were used for the same things synonymously,
this is an issue mostly in the context menus,
where eg. iOS had "Info" but desktop did not -
and android had an "i"-icon ...
but also, tapping 'Info' and then getting a different title
(not only a longer version) is not super-nice.
with this change, everything is "Info", making also the "i"-icon fit.
this is also consistent with WhatsApp.
Signal has the same mess as we before, at least on iOS.
came over that while targeting https://github.com/deltachat/deltachat-ios/pull/2204
and was shortly confused about what is going on there :)
(the name saved to database is not changed, however,
to avoid popping up the message again in case we do an update without a new device messase)
exiting 'select mode' is unexpected when hitting 'cancel' -
the user may still want to do other things with the selection.
this makes the 'mute' behavior consisten with other cases showing a dialog,
eg. 'delete'
link2xt