In a long text field with rich text formatting enabled, I write a text with line breaks:
When I exit the cell and come back, the line breaks are not present anymore:
Is it a normal behavior or a bug?
Here is what I would expect :
When I add line breaks in the field, it remains visible in Baserow after I exit the cell. Indeed, when there is a lot of text in a long text field, it can become really difficult to read without line break.
When I export/copy and paste outside Baserow, it keeps the line breaks as it is in the cell : if there is no line break, do not add line break (which is the case today) and if there are 2 line breaks in a row, keep the 2 line breaks in a row
Hi,
I just came across the same issue and I wish I had found it sooner.
I think it should be prioritized as it’s a deal breaker when using Baserow as a CMS for a website for example.
As a dev, I obviously can deal with it even if it’s not ideal.
But my final client will not understand why the rich text in a Baserow cell is not looking the same as the corresponding text on the website.
Airtable handles it well, maybe you could check how they do?
We understand that this is an important feature. I see that the relevant issue hasn’t been scored yet. I’ll check with the team about when we expect to start working on it.
I’ll add my comment that this is very important to fix. I also started to move over content from our website to Baserow, but then was shocked that the Rich Text Field doesn’t actually support line breaks (or image markdown). It’s made the process of creating content ridiculously complicated. The only way around it is to use a regular Text Field and then hand type HTML, which is like going back 20 years in history. Also, you need to support Image markdown in the Rich Text Editor. Right now, you can’t put any images in the Rich Text. Basically, the Rich Text Editor is very primitive. I think Baserow is built with Nuxt, and I am certain Nuxt has some component that offers full support for All Markdown Features. I’ve seen it on other Nuxt applications, so this should be an easy fix actually. There are so many Rich Text Editors to choose from. Thanks.
Hey @willdante@ddsgad, I’ve checked with the team—we will do our best to implement this feature in Q1 2025. Since we have a long list of tasks to complete by the end of this year, we can’t commit to working on it before then, but we’ll prioritize shipping it as soon as possible.
