`)
* * *
1. Bold, italic, underline (no toolbar support), strikethrough (Markdown-only via ~~ ), links, blockquotes, code, checkbox (Markdown-only via ; toolbar support coming soon), bullet lists, number lists
2. Some convert to closest Markdown (e.g., s, strike, strong, b, em, i, code; u is specifically unsupported because it does not cook to an actual underline); others will be allowed as “html\_inline” nodes (e.g., kbd, sup, sub, small, big, del, ins, mark)
---
### Author:  [@lindsey](https://meta.discourse.org/u/lindsey)
#### Post date: [March 12, 2025, 11:50am UTC](https://meta.discourse.org/t/test-our-new-composer/352347/2 "2025-03-12T11:50:20Z")
---
### Author:  [@Shauny](https://meta.discourse.org/u/Shauny)
#### Post date: [March 12, 2025, 11:56am UTC](https://meta.discourse.org/t/test-our-new-composer/352347/3 "2025-03-12T11:56:59Z")
Looking good!
There are some issues with spoiler tags:
1. If you highlight some text and choose “Blur Spoiler”, it replaces the text with “This text will be blurred”, losing what you highlighted
2. Inline spoilers aren’t working, it puts them on a new line
3. No way to toggle a spoiler off again
---
### Author:  [@lindsey](https://meta.discourse.org/u/lindsey)
#### Post date: [March 12, 2025, 12:05pm UTC](https://meta.discourse.org/t/test-our-new-composer/352347/4 "2025-03-12T12:05:35Z")
Thanks Shaun, noted that in the OP that we have more work to do on spoilers.
---
### Author:  [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [March 12, 2025, 12:20pm UTC](https://meta.discourse.org/t/test-our-new-composer/352347/5 "2025-03-12T12:20:28Z")
I was waiting for this feature and it’s awesome Discourse finally made this step 👏
Only 1 thing for now: it looks bizarre to have such a narrow textarea to write our post.
Obviously I was very much used to the side-to-side view of the composer and preview, but this now looks… Weird. Maybe I just need time tho. Yeah, probably. 😄
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [March 12, 2025, 12:33pm UTC](https://meta.discourse.org/t/test-our-new-composer/352347/6 "2025-03-12T12:33:01Z")
_Fantastic_ **progress!** ❤
The _second_ thing I noticed is that the current style doesn’t visually **toggle** on (and off) in the **tool bar** even though it remains in effect. It would be _ **really** _ nice if the current style was **highlighted** until toggled _ **off.** _
That is all for **now**!
(Basing my feedback from grey amber theme)
---
### Author:  [@lindsey](https://meta.discourse.org/u/lindsey)
#### Post date: [March 12, 2025, 12:37pm UTC](https://meta.discourse.org/t/test-our-new-composer/352347/7 "2025-03-12T12:37:23Z")
> [@Canapin](#):
>
> Only 1 thing for now: it looks bizarre to have such a narrow textarea to write our post.
> [@merefield](#):
>
> The _second_ thing I noticed is that the current style doesn’t visually **toggle** on (and off) in the **tool bar** even though it remains in effect.
These are good call outs — right now, we’ve been focused primarily on the editor itself (where you actually type), but we do have planned improvements to the composer container and toolbar which should address these issues.
---
### Author:  [@darkpixlz](https://meta.discourse.org/u/darkpixlz)
#### Post date: [March 12, 2025, 12:44pm UTC](https://meta.discourse.org/t/test-our-new-composer/352347/8 "2025-03-12T12:44:53Z")
A bit of a strange defect but when the composer is open this happens to the reply indicator.
Illl fully test when I’m on desktop later but it looks promising.
---
### Author:  [@Arkshine](https://meta.discourse.org/u/Arkshine)
#### Post date: [March 12, 2025, 12:56pm UTC](https://meta.discourse.org/t/test-our-new-composer/352347/9 "2025-03-12T12:56:59Z")
Finally here! 😍 That’s a lot of work unfolded; fantastic job! That will be a significant pro for users who are uncomfortable with Markdown.
_Edgy_ upload issue:
If you’re uploading an image and switch to markdown, the upload markdown is not here and throws an error:
Reversely, uploading from markdown, then switching to the new editor doesn’t error, but the image doesn’t appear.
---
### Author:  [@renato](https://meta.discourse.org/u/renato)
#### Post date: [March 12, 2025, 12:59pm UTC](https://meta.discourse.org/t/test-our-new-composer/352347/10 "2025-03-12T12:59:25Z")
> [@Arkshine](#):
>
> If you’re uploading an image
I wonder if we should just block switching until the upload is done… we can potentially convert placeholders between editors, but it doesn’t seem _that_ useful.
---
### Author:  [@Arkshine](https://meta.discourse.org/u/Arkshine)
#### Post date: [March 12, 2025, 1:03pm UTC](https://meta.discourse.org/t/test-our-new-composer/352347/11 "2025-03-12T13:03:38Z")
Yes, my thoughts are the same. Blocking sounds like a good idea!
When uploading a big image with a slow connection, I could not help but test the switch until it’s done. 😄
---
### Author:  [@ChrisBeach](https://meta.discourse.org/u/ChrisBeach)
#### Post date: [March 12, 2025, 1:44pm UTC](https://meta.discourse.org/t/test-our-new-composer/352347/12 "2025-03-12T13:44:47Z")
New design looks great. I love how Discourse iterates over time, tries new ideas and involves the community.
Some subjective observations, if you’re looking for feedback:
- The alignment button (left/right) is an unconventional icon, and a feature that seems very niche. Since the icons wrap onto two lines on mobile, I would simply remove this feature. Likewise, the “insert date” feature is advanced/niche and could be hidden within the ⚙ menu. That way the remaining icons would all fit on a single line
- The video upload feature was confusing for me, even as a technical user. What would I supply in the “video source” box? Also, the buttons get a bit jumbled visually (see below)
- The “M” button (switching between raw text and preview) doesn’t reveal its purpose until you click it. There’s some spare space on the bottom of the composer between the 🗑 and GIF buttons and I think a preview button would make more sense down here. And you’d have room for the word “preview”
---
### Author:  [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [March 12, 2025, 2:06pm UTC](https://meta.discourse.org/t/test-our-new-composer/352347/13 "2025-03-12T14:06:59Z")
> [@ChrisBeach](#):
>
> alignment button (left/right)
> [@ChrisBeach](#):
>
> video upload
These are features we’ve enabled on meta at some point, probably for an experiment. They are not available by default and we could turn them off or stick them behind the ⚙
> [@ChrisBeach](#):
>
> “insert date” feature is advanced/niche and could be hidden within the ⚙ menu.
I agree with this. Not sure why we always include this so prominently in the menu. I use it all the time myself but I also frequently use alot of features behind the ⚙ menu too!
> [@ChrisBeach](#):
>
> “M” button (switching between raw text and preview) doesn’t reveal its purpose until you click it.
Agree that at least mouseover helper text would help with discoverability here.
Down the road I suspect we’ll want to default to the new composer and make switching to markdown the power move, which power users will then know or be able to discover.
---
### Author:  [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [March 12, 2025, 2:54pm UTC](https://meta.discourse.org/t/test-our-new-composer/352347/14 "2025-03-12T14:54:57Z")
> 📣 These menu items are not really related to the new composer so we don’t need to focus on them here. If folks have more feedback about the menu items, please start new #Contribute > Feature topics or do a search.
That said:
- I removed the “Insert video” button here on meta, which is provided through the [Insert Video](https://meta.discourse.org/t/insert-video/147651) theme component.
- The “Toggle direction” button depends on the `support mixed text direction` site setting which we will keep enabled on meta because we are actively testing multilingual functionality currently.
- On meta we also have GIF and Ask AI which we want to allow prominent access to.
---
### Author:  [@dsims](https://meta.discourse.org/u/dsims)
#### Post date: [March 12, 2025, 3:03pm UTC](https://meta.discourse.org/t/test-our-new-composer/352347/15 "2025-03-12T15:03:06Z")
Congrats team! I did notice a discrepancy around oneboxing. Pasting a url from the browser generates a onebox, but typing it out does not. Until you swap back to see the markdown preview which triggers it to generate.
test: Pasting from browser bar here: [https://google.com/](https://google.com/) Typing here: [https://google.com](https://google.com)
---
### Author:  [@dfabulich](https://meta.discourse.org/u/dfabulich)
#### Post date: [March 12, 2025, 4:53pm UTC](https://meta.discourse.org/t/test-our-new-composer/352347/16 "2025-03-12T16:53:31Z")
Pressing Return in the new WYSIWYG composer creates a double-line break (a paragraph break). I don’t like it (though I guess this is subjective), but I especially don’t like it for bulleted/numbered lists, where there’s a ton of space between list items.
- this
- is
- too
- much
---
### Author:  [@Arkshine](https://meta.discourse.org/u/Arkshine)
#### Post date: [March 12, 2025, 4:59pm UTC](https://meta.discourse.org/t/test-our-new-composer/352347/17 "2025-03-12T16:59:30Z")
You can do shift + enter to avoid the double-line break, though it doesn’t work for lists.
I agree this behavior change should not be the default.
---
### Author:  [@darkpixlz](https://meta.discourse.org/u/darkpixlz)
#### Post date: [March 12, 2025, 5:04pm UTC](https://meta.discourse.org/t/test-our-new-composer/352347/18 "2025-03-12T17:04:23Z")
Great work, this is a step in the right direction! However, I still have some basic UX issues which I wish were solved, but I’ll get into that later.
The good:
I love the new single-editor mode, it’s really cool and inline images in the composer work great.
Even though this is a preview it still works as I would expect, I haven’t noticed anything missing personally (besides `---` which i use a lot)
The bad:
Buttons being all over the place here is confusing, there should be one place for all of them. Replace the double down arrow icon with an X. Also, instead of \<\< possibly it could just be Y axis draggable so we can control its size isnstsd if just one or closed?
I still really dislike the row of icons at the top and the “more” gear menu, it’s cluttered and confusing to use. I remember there being a topic on it to some degree but I cannot find it.
On my work computer (windows firefox) the markdown button is offset.
Still great I just wish these were fixed 👍
---
### Author:  [@lindsey](https://meta.discourse.org/u/lindsey)
#### Post date: [March 12, 2025, 5:13pm UTC](https://meta.discourse.org/t/test-our-new-composer/352347/19 "2025-03-12T17:13:30Z")
> [@dsims](#):
>
> Pasting a url from the browser generates a onebox, but typing it out does not. Until you swap back to see the markdown preview which triggers it to generate.
> [@darkpixlz](#):
>
> I haven’t noticed anything missing personally (besides `---` which i use a lot)
Added to our **🎨 UX issues** secton in OP to fix.
> [@dfabulich](#):
>
> I don’t like it (though I guess this is subjective), but I especially don’t like it for bulleted/numbered lists, where there’s a ton of space between list items.
This is a known missing feature and something we intend to add support for:
> [@lindsey](#):
>
> Tight list support (all lists are currently “loose”, meaning there’s extra padding between list items)
> [@darkpixlz](#):
>
> The bad:
> Buttons being all over the place here is confusing, there should be one place for all of them. Also, replace the double down arrow icon with an X. Also, instead of \<\< possibly it could just be Y axis draggable so we can control its size isnstsd if just one or closed?
> [@darkpixlz](#):
>
> I still really dislike the row of icons at the top and the “more” gear menu, it’s cluttered and confusing to use. I remember there being a topic on it to some degree but I cannot find it.
We are planning improvements to the composer container and toolbar, but right now the changes are limited to the editor itself. We can keep this in mind for those future changes though.
> [@darkpixlz](#):
>
> On my work computer (windows firefox) the markdown button is offset.
>
> 
I can’t tell from this description or screenshot what’s gone wrong here exactly — could you share a few more details so I can take a look?
---
### Author:  [@darkpixlz](https://meta.discourse.org/u/darkpixlz)
#### Post date: [March 12, 2025, 5:14pm UTC](https://meta.discourse.org/t/test-our-new-composer/352347/20 "2025-03-12T17:14:51Z")
> [@lindsey](#):
>
> I can’t tell from this description or screenshot what’s gone wrong here exactly — could you share a few more details so I can take a look?
Could just be visual but at least to me it looks like it is too far up by a little bit.
[Next page](https://meta.discourse.org/t/test-our-new-composer/352347.md?page=2)