# Depending how you opened the composer, may not close with no content

**URL:** https://meta.discourse.org/t/depending-how-you-opened-the-composer-may-not-close-with-no-content/75968
**Category:** UX
**Created:** [December 13, 2017, 4:03pm UTC](https://meta.discourse.org/t/depending-how-you-opened-the-composer-may-not-close-with-no-content/75968 "2017-12-13T16:03:38Z")
**Posts on this page:** 1
**Showing post:** 3

<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: [December 14, 2017, 5:28pm UTC](https://meta.discourse.org/t/depending-how-you-opened-the-composer-may-not-close-with-no-content/75968/3 "2017-12-14T17:28:58Z")

</div>

> [@codinghorror](#):
>
> This is VERY VERY specific to this exact trigger.

It also requires you to use Esc when closing it. Using the down chevron in the top right also does not cause the issue. So VERY VERY **VERY** specific.

It just happens to be how I use the composer, so I noticed it. Only started occurring after [If title has been added, composer should only be minimised, not terminated - #10 by neil](https://meta.discourse.org/t/if-title-has-been-added-composer-should-only-be-minimised-not-terminated/74591/10) as far as I can tell after.

---

_[View the full topic](https://meta.discourse.org/t/depending-how-you-opened-the-composer-may-not-close-with-no-content/75968)._
