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

<div class="post-metadata">

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

</div>

> [@sam](#):
>
> 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.

True! I’m actually a believer in getting rid of as many “are you sure” prompts as possible – as research has shown, no-one reads popups – in favour of “undo” opportunities. So perhaps discarding the draft (whether or not this button includes text) could then show a banner at the bottom for 5-10s?

> Draft Discarded. Undo

---

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