# 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:** [2017 年 11 月 29 日午後 12:52 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:** 3

<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:** [2017 年 11 月 29 日午後 10:43 UTC](https://meta.discourse.org/t/no-warning-before-destroying-draft-when-composer-is-minimized/75046/3 "2017-11-29T22:43:08Z")

</div>

That’s the way we originally designed it, as I recall, so not a bug. Our thinking was once you’ve minimized the composer you’re in experienced user mode and shouldn’t get a lot of extra nag dialogs.

---

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