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

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [November 30, 2017, 1:05am UTC](https://meta.discourse.org/t/no-warning-before-destroying-draft-when-composer-is-minimized/75046/9 "2017-11-30T01:05:47Z")

</div>

I first would like to get a sense of how real a problem this is, versus imagineering based on an imagined problem .. I need to hear stories from people who _actually_ lost their work. Because there’s two actions you need to take here:

1. minimize composer, already rare
2. click the tiny X at far far _far_ right

Not opposed to a change, per se, but I don’t like doing work speculatively.

---

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