# Composer tip under specific tag topics

**URL:** https://meta.discourse.org/t/composer-tip-under-specific-tag-topics/255618
**Category:** Theme component
**Created:** [February 19, 2023, 5:42pm UTC](https://meta.discourse.org/t/composer-tip-under-specific-tag-topics/255618 "2023-02-19T17:42:33Z")
**Posts on this page:** 1
**Showing post:** 16

<div class="post-metadata">

### Author: ![Heliosurge](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/heliosurge/32/571810_2.png) [@Heliosurge](https://meta.discourse.org/u/Heliosurge)
#### Post date: [February 21, 2023, 2:29am UTC](https://meta.discourse.org/t/composer-tip-under-specific-tag-topics/255618/16 "2023-02-21T02:29:45Z")

</div>

You would likely need to target them with css much like your targetting your element here.

In UX category there is a neat idea code that moves the composer menu on mobile to bottom with rhe gear having Options replace composer icons scrolling left to right. It would also have a placement issue with your component and chars requirement plugin.

Thanks for the speedy reply.

Here is the topic if your interested.

> [@Composer button bar suggestions](https://meta.discourse.org/t/composer-button-bar-suggestions/251059):
>
> Hello, This is a common issue on our forum. The native mobile context menu and selection is make complicate to use the editor button bar. So I made some hacky changes (need more work) but I think this is good, for an idea… slightly_smiling_face I show an example. Context menu covers the editor button bar. Selection and contextmenu covers the options popup menu I moved the editor button bar…

---

_[View the full topic](https://meta.discourse.org/t/composer-tip-under-specific-tag-topics/255618)._