element-hq / element-hq/element-web
Sign-out sequence is very confusing
- Dominant language
- TypeScript
- Stars
- 13.5k
- Forks
- 2.8k
- PR merge metrics
- PR metrics pending
Description
This looks like a bug, but I'm not sure. It's at least a bad confusion during the sign out sequence, which I find very confusing.
The buttons say:
1. I don't want my encrypted messages (but I do)
2. Start using Key backup

I'm confused on at least two levels. Every time I log out I'm asked to make a key. Why?
I already have a key from the last time I did this. The system doesn't seem to know that it's using that key in order to encrypt/decrypt all of the messages currently being typed and read. So it forces me to save another, which I do. I save it to the hard drive right next to the old file. That's confusing.
Then I discover there is no way to actually close the app without making an illogical button choice, which is button 1 above. If I just saved down my key protecting my ability to encrypt and decrypt all that I have produced in all rooms in Element, there should be another choice for gracefully exiting the app whilst observing that the app itself is correctly tracking reality (what I have done to enable it to encrypt/decrypt). That tracking is not reflecting in the the current UX.
This need to sign out was caused by a bug in which I am unable to see my latest typed message at the bottom of the message list. Instead, it is inserted just before the last message in the list, which message I'm unable to delete (the menu item is gone).
Also, the text editor almost two months after the bug report, continues to be broken in the same way: new lines are not shown for text exceeding the vertical confines of the message box. These lines only become visible when the first character is typed.
Contributor guide
Assessment
This issue has not been assessed yet.