Potential New Composer Issue: BBCode interpretation?

Bug
1

Hello! Currently, the default text when you open up the new composer indicates that you can enter Markdown, BBCode or HTML. It certainly seems to work with Markdown and HTML, but with BBCode, for example:

[b]Test[/b]

Perhaps this just means that the rich text editor doesn’t accept BBCode after all, or isn’t meant to that is?

Edit

Well, in playing around with this, I’ve noticed some weird behaviour that can be reproduced on the boards here! The first is that BBCode seems to be interpreted inconsistently…for example:

[b]Bold is not automatically transformed…[/b]

Underline is, however!

The problem is, if you enter some underlined text, then (for example) delete all text from the composer and start typing again, that text will still be underlined. If you switch the new composer on and off quickly, the problem goes away. :thinking: None of the other BBCode tags that I’ve tried have been interpreted, so I’m not sure if underline working is just a coincidence, or if the composer is meant to support BBCode and is just having some problems. :slight_smile:

3

BBCode is only supported if you write from markdown editor.
If you type [b] in the rich text editor, it will get escaped and not get transformed into bold. Same behavior with underline, you just must have been confused when switching from one mode to another.

3 Likes
5

Thank you for clarifying :slight_smile: Since the prompt indicates that BBCode can be entered, I just assumed that the new composer would accept it, so apologies for the mistake there!

I can say from testing on my own site and the boards here, however, underline is definitely converted by the new composer. If I start typing

[u]

It is automatically converted to underlined text by the new composer. I guess this is not the intended behaviour after all?