# 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:** [29 نوفمبر 2017، 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:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![Pad\_Pors](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pad_pors/32/52016_2.png) [@Pad\_Pors](https://meta.discourse.org/u/Pad_Pors)
#### Post date: [29 نوفمبر 2017، 12:52م UTC](https://meta.discourse.org/t/no-warning-before-destroying-draft-when-composer-is-minimized/75046/1 "2017-11-29T12:52:10Z")

</div>

not sure if this has anything to do with the new composer, but it seems that drafts (both posts and topics) are not saved anymore if I press the close button here:

 ![image](https://global.discourse-cdn.com/meta/original/3X/e/0/e0008e1b03de0e5908ebf635ff8bd083b98fb03a.png)

---

<div class="post-metadata">

### Author: ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [29 نوفمبر 2017، 5:07م UTC](https://meta.discourse.org/t/no-warning-before-destroying-draft-when-composer-is-minimized/75046/2 "2017-11-29T17:07:00Z")

</div>

That one seems like a bug to me. The X functions like the cancel button (destroying the draft) but does not have a confirmation dialog warning of this.

---

<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: [29 نوفمبر 2017، 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.

---

<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: [30 نوفمبر 2017، 12:09ص UTC](https://meta.discourse.org/t/no-warning-before-destroying-draft-when-composer-is-minimized/75046/4 "2017-11-30T00:09:18Z")

</div>

I 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. Yes, you’ll probably only make the mistake of clicking this once or twice, but it’s unlikely to be a happy experience when you do. 😉 By changing it to text, you can still avoid having nag dialogs.

---

<div class="post-metadata">

### Author: ![awesomerobot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/awesomerobot/32/142900_2.png) [@awesomerobot](https://meta.discourse.org/u/awesomerobot)
#### Post date: [30 نوفمبر 2017، 12:14ص UTC](https://meta.discourse.org/t/no-warning-before-destroying-draft-when-composer-is-minimized/75046/5 "2017-11-30T00:14:05Z")

</div>

I was just thinking that but you beat me to it. I do agree that adding another confirmation makes it kind of a lot — at that point you’re collapsing, clicking the x, and then confirming.

 ![37 PM](https://global.discourse-cdn.com/meta/original/3X/c/0/c031c97bb8937993922ad1e5dbb71424391fb0c0.png)

---

<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: [30 نوفمبر 2017، 12:16ص 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.

---

<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: [30 نوفمبر 2017، 12:41ص 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

---

<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: [30 نوفمبر 2017، 12:45ص 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

---

<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: [30 نوفمبر 2017، 1:05ص 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.

---

<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: [30 نوفمبر 2017، 1:30ص UTC](https://meta.discourse.org/t/no-warning-before-destroying-draft-when-composer-is-minimized/75046/10 "2017-11-30T01:30:33Z")

</div>

The tooltips were atrocious, it said: “hide or show the composer panel”, which is 100% incorrect for when it is collapsed.

[https://github.com/discourse/discourse/commit/bf1f6c7fe48fabf9ea32804090ac8ea46bec16ab](https://github.com/discourse/discourse/commit/bf1f6c7fe48fabf9ea32804090ac8ea46bec16ab)

So I fixed the bad tooltip, and also added the nag cause it was a trivial change. If people complain about the new nag I guess we can revert to a non naggy X.

Next up, fix the atrocious tooltip when I hover over blue 1 or green 1

---

<div class="post-metadata">

### Author: ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [2 ديسمبر 2017، 2:30ص UTC](https://meta.discourse.org/t/no-warning-before-destroying-draft-when-composer-is-minimized/75046/14 "2017-12-02T02:30:43Z")

</div>


