-
-
Notifications
You must be signed in to change notification settings - Fork 784
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Save draft messages when switching channels #3340
Comments
The |
jcbrand
added a commit
that referenced
this issue
Mar 31, 2025
jcbrand
added a commit
that referenced
this issue
Apr 1, 2025
jcbrand
added a commit
that referenced
this issue
Apr 1, 2025
- Refactor message correction - Play well with message quoting
jcbrand
added a commit
that referenced
this issue
Apr 2, 2025
- Refactor message correction - Play well with message quoting
jcbrand
added a commit
that referenced
this issue
Apr 3, 2025
- Refactor message correction - Play well with message quoting
jcbrand
added a commit
that referenced
this issue
Apr 3, 2025
- Refactor message correction - Play well with message quoting
jcbrand
added a commit
that referenced
this issue
Apr 3, 2025
- Refactor message correction - Play well with message quoting
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
When switching to a different MUC or contact, anything I wrote in the entry box is lost.
Video demonstration
Describe the solution you'd like
When switching channels, instead of deleting the current draft message, it should be saved and restored when going back to the same channel. This should preferably be done in a way that would be saved in the browser local storage and survive a browser restart.
I don’t know where drafts should be saved in the code yet.
Describe alternatives you've considered
A (possibly) somewhat easier to implement option is to never delete anything from the text entry field, and keep the draft when switching channels, but I feel that this would be unexpected and unnatural for most users.
The text was updated successfully, but these errors were encountered: