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

[UI nitpick] replying shouldn't necessarily nuke the drafted toot #18743

Open
SoniEx2 opened this issue Jun 30, 2022 · 1 comment
Open

[UI nitpick] replying shouldn't necessarily nuke the drafted toot #18743

SoniEx2 opened this issue Jun 30, 2022 · 1 comment
Labels
suggestion Feature suggestion

Comments

@SoniEx2
Copy link

SoniEx2 commented Jun 30, 2022

Pitch

Replying shouldn't necessarily nuke the drafted toot.

Motivation

Particularly when appending to a top-level thread, honestly. It's kinda inconvenient. (We'd even argue getting out of reply shouldn't nuke the toot but that discussion has already been had. It'd be nice to have a proper, separate "nuke toot" option tho, regardless of replying or whatever. In fact, twitter does have such an option - if you press escape, it asks if you wanna nuke the drafted tweet. But yeah, being able to losslessly carry the same drafted toot between various states (reply, top-level, threaded) would be cool.)

additional keywords: keep

@SoniEx2 SoniEx2 added the suggestion Feature suggestion label Jun 30, 2022
@realpixelcode
Copy link

Totally agree. I often come across this issue when viewing another post in the single layout, so I forget to actually click the Reply button before typing anything into the draft box.

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

No branches or pull requests

2 participants