# Help Us Test the Composer Redesign
**URL:** https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849
**Category:** Announcements
**Tags:** composer, design
**Created:** [August 6, 2026, 8:40am UTC](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849 "2026-08-06T08:40:30Z")
**Posts on this page:** 20
**Page:** 2
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [August 7, 2026, 3:28am UTC](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/23 "2026-08-07T03:28:27Z")
If the category name is too long, the tag button gets cut off.
Is it possible to show a numerical count of tags added after 1 or more tags are added, next to the icon? That seems better than having the tag icon filled now (it’s very subtle).
I think Canapin brought this up: the title feels quite cut off for some reason; it might have to do with the floating button in the way.
---
### Author:  [@Heliosurge](https://meta.discourse.org/u/Heliosurge)
#### Post date: [August 7, 2026, 4:13am UTC](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/24 "2026-08-07T04:13:25Z")
When enabling Composer Redesign. Choosing Staff or Specific Groups did not work. I had to choose everyone
---
### Author:  [@martin](https://meta.discourse.org/u/martin)
#### Post date: [August 7, 2026, 5:54am UTC](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/25 "2026-08-07T05:54:07Z")
Odd, did you get any error or anything? We have it set to a specific group here on Meta:
---
### Author:  [@Heliosurge](https://meta.discourse.org/u/Heliosurge)
#### Post date: [August 7, 2026, 6:02am UTC](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/26 "2026-08-07T06:02:02Z")
I didn’t see an error but can try retesting i first tried to set it to specific groups Staff, Guide
When I tested composer it was unchanged. So I tried the Staff only option with same effect. Only once I enabled for everyone did it show the redesigned composer in mobile
I haven’t tested in desktop. I apologize as I forgot to add extra details
Mobile on Google Pixel 9 XL.
**EDiT** just retried those settings. Working now! May have been viewing cached forum? I had even tried refreshing. But all good now
🍻 😎👍✨
---
### Author:  [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [August 7, 2026, 12:53pm UTC](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/28 "2026-08-07T12:53:54Z")
Very minor design oversight. When active, the selector’s background has rounded border whereas there aren’t visible rounded borders on the default state:
---
### Author:  [@sk-or-v1-contents](https://meta.discourse.org/u/sk-or-v1-contents)
#### Post date: [August 8, 2026, 4:20am UTC](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/29 "2026-08-08T04:20:45Z")
I know this has been said before but [I really hope the preview button can be brought back on mobile](https://meta.discourse.org/t/cannot-view-post-preview-in-mobile-composer/408352). One of the forums I use doesn’t have enough community push to install the [component workaround](https://meta.discourse.org/t/mobile-composer-preview/408784).
> [@chapoi](#):
>
> C) How does the animation for the expanding editor work on your device?
It’s kinda flashy, and flashes blue when expanding due to the Chromium-characteristic blue highlight(?).
Besides that I need to tap the minus button twice to minimize when keyboard is launched. (note: not present in old design) This might be caused by this glitch in this video frame (seen after tapping minus button the first time), where the URL bar jumps up to the position of minus button for unknown reason:
---
### Author:  [@Noble\_Fish](https://meta.discourse.org/u/Noble_Fish)
#### Post date: [August 9, 2026, 4:46am UTC](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/30 "2026-08-09T04:46:20Z")
It seems to work well on _Foundation_, but there are some issues on _Horizon_: the preview window has a border with the accent color.
- Currently, during testing, this issue appears to occur only when creating new topics.
---
### Author:  [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [August 9, 2026, 8:10am UTC](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/31 "2026-08-09T08:10:50Z")
> [@Noble\_Fish](#):
>
> eems to work well on _Foundation_, but there are some issues on _Horizon_
Glad it works well on Foundation! For Horizon, Yes I know, as I said in OP
> [@chapoi](#):
>
> how it works on regular screen sizes (desktop & mobile) on Foundation. Tablets, folding phones, other themes, and so on have not been optimised yet.
Im still working on it.
---
### Author:  [@sk-or-v1-contents](https://meta.discourse.org/u/sk-or-v1-contents)
#### Post date: [August 9, 2026, 10:48am UTC](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/32 "2026-08-09T10:48:16Z")
I asked AI and the blue flash can be fixed by adding `-webkit-tap-highlight-color: transparent` to the element in question. I’d recommend doing that for the editor element because when it occupies full screen when expanding, it results in fullscreen flash, not good visual feel.
---
### Author:  [@sk-or-v1-contents](https://meta.discourse.org/u/sk-or-v1-contents)
#### Post date: [August 9, 2026, 10:53am UTC](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/33 "2026-08-09T10:53:40Z")
This is how it looks like if I apply `* {-webkit-tap-highlight-color: transparent}` with Stylus (I’m using Edge on Android)
---
### Author:  [@per1234](https://meta.discourse.org/u/per1234)
#### Post date: [August 9, 2026, 9:28pm UTC](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/34 "2026-08-09T21:28:04Z")
I think the borderless design is significantly less intuitive:
The title appears to be part of the post body editor. Fine. But if I type the title and then press the **Enter** key, the cursor doesn’t move to the next line. It feels like I’m just stuck on the first line of the post without any way to progress. I don’t think the user will intuitively understand they must click on the next line or press **Tab** to continue. If you want to make title input part of the post body editor, then it must work just like any other line in the editor. If it is going to continue to be treated as a separate input field, then go back to the old design where that nature was visually communicated to the user.
The lack of a border between the post editor and the preview (when the composer is in markdown editor mode) is too confusing. These are two separate panels. That fact should be visually communicated to the user by a border between the two.
---
### Author:  [@per1234](https://meta.discourse.org/u/per1234)
#### Post date: [August 9, 2026, 10:04pm UTC](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/35 "2026-08-09T22:04:36Z")
There is no right margin on the preview that is shown when the composer is in “markdown editor mode”:
I would expect it to have a margin similar to the one we see on the left side of the composer, as we see when the composer is in “rich text editor mode”:
---
### Author:  [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [August 10, 2026, 8:13am UTC](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/36 "2026-08-10T08:13:26Z")
> [@per1234](#):
>
> But if I type the title and then press the **Enter** key, the cursor doesn’t move to the next line. It feels like I’m just stuck on the first line of the post without any way to progress.
@renato Do you think that’s easy enough to achieve?
---
### Author:  [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [August 10, 2026, 8:48am UTC](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/37 "2026-08-10T08:48:06Z")
If it does, should it also go the other way? If the cursor is at the beginning of the textarea, pressing back should go to the title input then?
Those being distinct fields, I’d find this whole behavior (title to textarea and vice versa) bizarre, but perhaps I’d change my mind after using it.
---
### Author:  [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [August 10, 2026, 4:53pm UTC](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/38 "2026-08-10T16:53:30Z")
Just FYI, and perhaps too soon and already known, but the toolbar is totally missing when ~~using mobile/iPhone on DiscourseHub~~
**Edit**
It has nothing to do with DiscourseHub. It follows visibility status of the the toolbar of original composer.
If the toolbar is hided via the toggle, and then new composer is enabled, the toolbar isn’t visible and there is no way AFAIK to show it. And vice versa. If original one has visible toolbar, then changing to new composer offers the toolbar.
---
### Author:  [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [August 11, 2026, 12:33pm UTC](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/39 "2026-08-11T12:33:42Z")
Hello all and thanks for all the feedback so far.
Few things I’ve implemented/fixed: (merge pending)
-
> [@Don](#):
>
> think adding a visual grip/handle could help indicate this to users.
-
> [@NateDhaliwal](#):
>
> If the category name is too long, the tag button gets cut off.
-
> [@Canapin](#):
>
> When active, the selector’s background has rounded border whereas there aren’t visible rounded borders on the default state
-
> [@sk-or-v1-contents](#):
>
> Besides that I need to tap the minus button twice to minimize when keyboard is launched.
-
> [@per1234](#):
>
> There is no right margin on the preview that is shown when the composer is in “markdown editor mode”:
- Reformatted the title back to a separate input-like section. Might revisit later.
Now working on:
-
> [@NateDhaliwal](#):
>
> s it possible to bring down the topic content editor when the keyboard is closed?
-
> [@NateDhaliwal](#):
>
> Is it possible to show a numerical count of tags added after 1 or more tags are added, next to the icon?
-
> [@sk-or-v1-contents](#):
>
> It’s kinda flashy, and flashes blue when expanding due to the Chromium-characteristic blue highlight(?).
I’ll keep following this topic – still thinking through some of the other feedback.
> [@Jagster](#):
>
> It has nothing to do with DiscourseHub. It follows visibility status of the the toolbar of original composer.
Yes I figured this was the issue – shouldn’t be an issue once the redesign is properly implemented (ie toggle is no longer functional)
---
### Author:  [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [August 11, 2026, 5:14pm UTC](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/40 "2026-08-11T17:14:47Z")
Slightly off-topic since it’s also the case on the “old” composer, but I noticed that when I drag the composer up and down, it’s following the cursor late, and has a choppier animation.
Play at 0.25× speed to see better what I’m talking about.
[ ](https://www.youtube.com/watch?v=El11dhyJNkQ)
I suspect it’s a JS/browser limitation and that nothing can be easily optimized?
I’d love to see interface elements reacts near instantly and being animated at 60 fps.
* * *
Besides this, after using the new composer for a few days, it’s just better. It has a few “flaws” people agree on (markdown/preview separation, title…), but overall it’s a very nice improvement to something I think is hard to improve. So, great job 🥳
---
### Author:  [@sterretje](https://meta.discourse.org/u/sterretje)
#### Post date: [August 15, 2026, 6:00am UTC](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/43 "2026-08-15T06:00:01Z")
The new composer takes a lot of vertical real estate. I now have to increase its size when composing a new topic. This is less of an (or no) issue when replying to a post.
FYI
Using the markdown editor, Firefox on Win11
---
### Author:  [@nickdb](https://meta.discourse.org/u/nickdb)
#### Post date: [August 15, 2026, 10:24am UTC](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/44 "2026-08-15T10:24:38Z")
Hi, a couple of observations.
We use the mermaid plugin to display nodered flows. This does not work in this new or the previous rich text editor. Code is showed as console text:
We could previously work around this by switching the composer back to the older, non-rich text variant. This selection button no longer works.
EDIT: Nevermind. On a full page reload the button starts to work again and in the standard markup editor mermaid works, though not in the rich text version.
Must be a beta-safarism.
(Safari, Mac OS 27 current public beta)
---
### Author:  [@sk-or-v1-contents](https://meta.discourse.org/u/sk-or-v1-contents)
#### Post date: [August 15, 2026, 12:19pm UTC](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849/45 "2026-08-15T12:19:31Z")
> [@sk-or-v1-contents](#):
>
> Besides that I need to tap the minus button twice to minimize when keyboard is launched.
Fixed now 🙂
> [@sk-or-v1-contents](#):
>
> the URL bar jumps up to the position of minus button for unknown reason
Info update: This still occurs with Sogou keyboard customized for Xiaomi, but not with Fcitx keyboard. I am ditching quirky Sogou anyway so won’t call to make that keyboard a priority
[Previous page](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849.md?page=1)
[Next page](https://meta.discourse.org/t/help-us-test-the-composer-redesign/407849.md?page=3)