Back to Changelog

April 17, 2024

Rich Text Improvements

Solved the most frustraiting part of WYSIWYG editors, plus added formatting constraints.

We’ve pushed two improvements to our Rich Text Block.

  1. Added an indicator to marks that tells you if you’re editing inside or outside of it.

  2. Added a way to enable/disable specific formatting.

Mark Indicators

Note: “mark” refers to formatting that’s applied on characters, such as making something bold, or italic, or having inline code.

One of the most frustrating parts of WYSIWYG editors is the way marks work. Let’s say you have something marked as bold. Then, to go back and add something right before it, you’ll need to struggle with your editor sometimes adding the text inside of the mark (marking it as bold), or vice versa. This is how it works in Slack:

The whole thing is unpredictable and hard to explain, but we’ve all experienced it.

We had this same issue in our own Rich Text editor, and we simply couldn’t live with it. This is how you edit marks now:

Allowed Formatting

Before this update, editors could apply any type of formatting to Rich Text Blocks. Headings, lists, images, videos, etc… were all available, always.

We heard from developers that sometimes it’s very useful to limit which formatting can be applied, so the rendering stays consistent. For example, you may want to limit blog posts’ contents to not support H1, and only support H2 and H3. Or you may not want to support tables, or videos. You get the idea!

Now, you can do so within the Rich Text’s properties panel.