# 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:** 8

<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:45am UTC](https://meta.discourse.org/t/no-warning-before-destroying-draft-when-composer-is-minimized/75046/8 "2017-11-30T00:45:32Z")

</div>

Also a giant fan of “Undo” but that would now make this a much more giant change to make for pretty much an edge case.

Edge case being:

- I just typed a bunch of paragraphs
- I was on the fence about throwing them away, so I minimized the composer
- A minute later I clicked X cause I decided yeah … I really should throw my paragraphs away

I think the more common flow is:

- I just typed a bunch of paragraphs
- I decided they are pointless
- I hit cancel
- I get a nag

---

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