# No warning before destroying draft when composer is minimized

**URL:** <https://meta.discourse.org/t/no-warning-before-destroying-draft-when-composer-is-minimized/75046>\
**Category:** UX\
**Created:** [November 29, 2017, 12:52pm UTC](https://meta.discourse.org/t/no-warning-before-destroying-draft-when-composer-is-minimized/75046 "2017-11-29T12:52:10Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [November 30, 2017, 12:16am UTC](https://meta.discourse.org/t/no-warning-before-destroying-draft-when-composer-is-minimized/75046/6 "2017-11-30T00:16:20Z")

</div>

I can confirm this is not a regression but think this is inconsistent, Cancel nags, X should nag as well. It is quite easy to hit X by mistake.

I have pretty much never hit X on the composer minimized and **intended** it to throw away my draft.

> [@barryvan](#):
>
> wonder if, when the composer is minimised like this, the button should change from an icon to text; something like “Discard” would make it clearer what this is doing.

I actually oppose to that unless we add a nag, cause you are making the click area even bigger at that point increasing the chances of a “X” by mistake.

---

_[View the full topic](https://meta.discourse.org/t/no-warning-before-destroying-draft-when-composer-is-minimized/75046)._