Temporary messages are local messages that show up in the chat view as soon as the user hits enter. For now, while waiting for the server response we display a little spinner instead of the message time. Once we get a confirmation from the server we display the timestamp. Atm we don't handle unsent messages.

Things to do:
^ for this last one I'm not sure how to display the warning.. Red text on top of the message? Red message? What do you think @nextcloud/designers-talk @nextcloud/talk? Also I was thinking to display the delete and retry actions explicitly (no 3 dot menu) on the right.
btw @nickvergessen check out the date :see_no_evil:
What about a small airplane icon while sending turning into a small checkmark when sent?
I remember Jan suggesting for something similar :thinking:
Signal does it very well, with
Regarding errors, we can show an error icon in place of the spinner. Tapping it can open a menu with a short error info, "Retry send" and "Delete".
What about a small airplane icon while sending turning into a small checkmark when sent?
@skjnldsv I think that the spinner conveys a sense of 'pending stuff to be done' much better than the airplane icon does
2 circled and filled checkmarks when read (if enabled)
What do you mean with this @jancborchardt? I thought we weren't going to support read confirmation.
Regarding errors, we can show an error icon in place of the spinner. Tapping it can open a menu with a short error info, "Retry send" and "Delete".
I like this :-)
We don't have support for anything other than the 3 dot icon for grouped actions atm, right @skjnldsv ?
@ma12-co I was simply describing what Signal does and including their design for indicating read state. :) Also, we never know if we will support it in the future.
We don't have support for anything other than the 3 dot icon for grouped actions atm, right @skjnldsv ?
You can use a custom icon now thanks to Georg :)
Though the icon-loading-small might require a tiny bit of css fixes, but give it a try!
well read checkmarkers are handled in https://github.com/nextcloud/spreed/issues/1012
The point of this issue is how to deal with failed sendings, to bring in missing parsing of mentions, and make sure the poster information is handled already
Just this one left:
- Set a timeout and add a warning if no response from the server is received.
Most helpful comment
Signal does it very well, with
Regarding errors, we can show an error icon in place of the spinner. Tapping it can open a menu with a short error info, "Retry send" and "Delete".