we skip this release and focus on 0.3

We now indicate that the content is missing and show a little text indicating if content is missing, is currently being loaded, or failed to be loaded.

I did all the moving around and we now have a single framework plugin. The one thing I did not yet do is move button etc to a controls subdirectory. I don't think it's necessary right now, but I'm open to follow up on that if that's wanted.

We need to release with 0.2:

• kasync (due to ciritical bugfixes that we rely on)

We're doing simple string autocompletion for the addressbook now.

In T1826#87121, @cmollekopf wrote:

While that may be true I think we still have to fix the issue of focusing a single mail as it will be equally relevant for keyboard navigation/shortcuts.

True, but I agree that adding more steps doesn't seem like a good idea for autocompletion. One benefit of the addressbook approach might be that it is much more touch-friendly than a list of email addresses (due to larger hitboxes).

In T1826#87116, @mbohlender wrote:

I think we can get away with marking the whole thread as unread once the user clicked on it and stayed on it for a short time.

I think we can get away with marking the whole thread as unread once the user clicked on it and stayed on it for a short time.

the other solution would be a two step process of selecting the person and then pic an address if there is more then one. I'd like to avoid additional steps where possible though.

We can use the mail status for this, just like we do for downloading messages.

I have experimented with ways to determine the current mail, which can then be used to mark the mail as read and implemented a first version.
It's fairly difficult to achieve a system that works reliably though. The system as it currently is always has a single mail as current mail (and all other mails get slightly grayed out to indicate that). The current implementation only set's the current index based on the scrolling position, which becomes problematic when we have many small mails in the conversation view (especially at the beginning and the end):

A problem we get with using the addressbook is that we don't have an easy way to deal with multiple addresses.
I therefore started to question whether we shouldn't rather just autocomplete email-addresses.
We could still supplement the email address with information from the addressbook (avatar, name, ...), but perhaps building a solution that is geared towards email addresses works better?