Yes this probably does need some design input, as none of the current designs have anything regarding this.
I think some sort of empty state would be a good thing to show here. It could possibly be better to do it as a static web page rather than in qml. As at the moment Dekko just loads "about:blank" to ensure it's empty, which could easily be changed for a different page.
The one thing we can't do is preselect a message that is still unread, as that will trigger an action to mark it as read on the server without any user interaction. Instead we could select the last opened/selected message before the previous session was quit. So you would only end up seeing the empty state the first time you open a mailbox or if the server informed us the message uid's have changed and we have to trash our current cache. I think they are the only two instances the empty state view would be needed.
Thanks for the report.
Yes this probably does need some design input, as none of the current designs have anything regarding this.
I think some sort of empty state would be a good thing to show here. It could possibly be better to do it as a static web page rather than in qml. As at the moment Dekko just loads "about:blank" to ensure it's empty, which could easily be changed for a different page.
The one thing we can't do is preselect a message that is still unread, as that will trigger an action to mark it as read on the server without any user interaction. Instead we could select the last opened/selected message before the previous session was quit. So you would only end up seeing the empty state the first time you open a mailbox or if the server informed us the message uid's have changed and we have to trash our current cache. I think they are the only two instances the empty state view would be needed.