Skip to content
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

Hiding a composer should explicitly save a draft #12245

Open
julianlam opened this issue Dec 25, 2023 · 0 comments
Open

Hiding a composer should explicitly save a draft #12245

julianlam opened this issue Dec 25, 2023 · 0 comments

Comments

@julianlam
Copy link
Member

When a composer is opened (either by attempting to create a new topic/post, or by editing an existing post), and immediately hidden, the composer disappears and it is not immediately apparent what happened to it.

Was it merely hidden, or actually discarded?

For better UX, either explicitly save a draft (even if nothing was changed), or throw an alert notifying the user that the draft was discarded as there was no content/changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant