# Why is Apply wrap so high up in the Composer Options menu?

**URL:** https://meta.discourse.org/t/why-is-apply-wrap-so-high-up-in-the-composer-options-menu/393028
**Category:** UX
**Created:** [January 9, 2026, 4:30am UTC](https://meta.discourse.org/t/why-is-apply-wrap-so-high-up-in-the-composer-options-menu/393028 "2026-01-09T04:30:28Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![nathank](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nathank/32/290039_2.png) [@nathank](https://meta.discourse.org/u/nathank)
#### Post date: [January 9, 2026, 4:30am UTC](https://meta.discourse.org/t/why-is-apply-wrap-so-high-up-in-the-composer-options-menu/393028/1 "2026-01-09T04:30:28Z")

</div>

This caused one of my users a problem today, as it pushed the `Build Poll` down off the visible options for them (and they didn’t realise that they had to scroll):

 ![image](https://global.discourse-cdn.com/meta/original/4X/5/0/0/50043873fa161d72f72338bd5ef6c7bd6a61d3bf.png)

In that example from Meta, `Build poll` is still visible (it seems a bit device / browser specific), but it does raise why `Apply wrap` is so prominent in the dropdown.

I can’t see this being used by anyone except power users; it really belongs down the bottom, doesn’t it?

Of note, this used to be called the Composer ‘gear’ menu.

---

<div class="post-metadata">

### Author: ![chapoi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chapoi/32/537252_2.png) [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [January 10, 2026, 9:32am UTC](https://meta.discourse.org/t/why-is-apply-wrap-so-high-up-in-the-composer-options-menu/393028/2 "2026-01-10T09:32:13Z")

</div>

@renato Fair question, I’ve wondered the same. Would it be easy enough to move this down?

In general, maybe we should look at the order here. “insert math” also feels like something that could move down a bit.

---

<div class="post-metadata">

### Author: ![Lilly](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lilly/32/575047_2.png) [@Lilly](https://meta.discourse.org/u/Lilly)
#### Post date: [January 10, 2026, 3:26pm UTC](https://meta.discourse.org/t/why-is-apply-wrap-so-high-up-in-the-composer-options-menu/393028/3 "2026-01-10T15:26:27Z")

</div>

> [@nathank](#):
>
> In that example from Meta, `Build poll` is still visible (it seems a bit device / browser specific), but it does raise why `Apply wrap` is so prominent in the dropdown.
> 
> I can’t see this being used by anyone except power users; it really belongs down the bottom, doesn’t it?

Ideally, the order of the items in that menu should be admin-configurable, since different forums have different user and formatting needs. i think you can do something like this to remove the vertical scrolling friction and force the menu to fit all items:

```scss
.fk-d-menu[class*=toolbar-menu].fk-d-menu {
    max-height: fit-content;
}

```

result:

 ![Screenshot 2026-01-10 at 7.39.58 AM](https://global.discourse-cdn.com/meta/original/4X/e/c/7/ec72b05d10c2264859d20a8ae572c352cf1dc9f0.png)

---

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [January 10, 2026, 4:13pm UTC](https://meta.discourse.org/t/why-is-apply-wrap-so-high-up-in-the-composer-options-menu/393028/4 "2026-01-10T16:13:13Z")

</div>

> [@Lilly](#):
>
> Ideally, the order of the items in that menu should be admin-configurable, since different forums have different user and formatting needs

Nat has suggested a setting for that too

> [@"Quote whole post" button location](https://meta.discourse.org/t/quote-whole-post-button-location/380263/2):
>
> One thing I found super pleasant was the introduction of the “post menu” site setting (/admin/site\_settings/category/all\_results?filter=post%20menu) by @saquetim. It essentially defines the order of items here below a post: @renato It could be really cool if this was an option for the composer. I think it may address some of the biggest composer requests on customizability.

It could be a little more complicated because plugins/components can add buttons, and these are probably difficult to configure in a site setting, just like this is a problem in the sidebar.
