Probable bug - Rich text block issues

Hi, I am using a rich text block to pull data from my Airtable database. Field is formatted as rich text editable in Airtable and has formatting like bold, line breaks, links, bullets and paragraphs.

Problems I am observing in Weweb,

  • Links never work (100% of the time)
  • Bolds are inconsistent
  • Line breaks don’t work

And then this… see the attached image… Half of it is rendering bold, other half showing the Markdown coding and not rendering properly. This is all the same block. Not sure this is even possible. Also none of the line breaks are rendered.

Happy to find out that i am making an error but Rich Text Block seems like a very half cooked and released function in the system.

for bold

you need to ensure there is no space between the first letter and last letter to bolded and its accompanying astrisk

*sdf* works while * sdf * will not

for the rest, we’d need to see your input value to the block to help out

That formatting is Airtable’s making, not my manual markdown code, it is interesting to know.

Below i copy pasted from Airtable, as you can see, lines are separated properly to this editor. But not rendered properly in Weweb.


Material Sourced using Organic Methods:

Cotton verified by Global Organic Textile Standard (GOTS),

Organic Content Standard (OCS).


Here is the editor image, fixing the space issue, no idea why line breaks and links do not work.

the issue is the formatting in your text. you need to remove. the white space beteen the : (colon) and the **(double. asterisk)

for newline issues, they’re weird but if you need more than 1 line space between paragraphs you include a <br> tag

test your markdown here

1 Like

Thanks super helpful.
Still cannot see any links being rendered properly, but will keep tinkering.

Is the necessity of the <br> tag intended for line breaks in rich text element? I’m working with a similar setup: rich text field in airtable pulling into WeWeb.

Screenshotted is the same data, top binded to a normal text element, bottom binded to a rich text element.

Note that the regular text element does correctly pick up the line breaks from the input data, while the rich text doesn’t (I added a <br> tag after the first line of data to test).

Before I go adding <br> tags across all my records, is this intended behavior of the rich text element? Or is there a more efficient way to get the desired output with the rich text element besides adding <br> in all my data? @Joyce

Arbitrary HTML is needed when you want an effect that isn’t covered by markdown conventions. But it looks like something else going on in here. Pulling the original JSON from the Airtable API request might give a lot more clarity. You can open dev tools on your browser, find the request, and pull that into a text file or some such so we can take a better look.