The RT field was imported from Zapier. I have a Push by Zapier extension in Chrome that grabs a webpage and pulls the related information from the site’s API which is then pushed from Zapier into a Webflow CMS draft item. I’m not sure how the line breaks are created on the source site or how Zapier interprets them. The line breaks, bullet points, and other formatting have always gotten lost in the process so I’ve had to go in to the Editor and manually add line breaks. With the changes to the rich text editor, the formatting seems to be intact. However, see below.
Thanks for the extra info, that’s actually super helpful
Both our new and old rich content editors work with a specific tag structure and have different ways of massaging random html into the structure it can work with. We currently do a lot more processing on paste because different apps create super chaotic html and html-like things in the clipboard. Eg. we had an issue where copying things from a webpage in Firefox added tons of unicode newlines to the clipboard… Either way it looks like we need to add more processing to csv import, zapier, the Webflow api for rich content fields.
Right now the new rich content editor is integrated in the Designer Canvas, Designer & Editor Data Managers (the CMS), but not yet in the Editor Canvas. While editing with the new one we add a css property
white-space: pre-wrap; which helps us resolve a bunch of cross-browser issues, but it also has the side effect of showing all the unicode newlines; and the edge spaces at the beginning/end of a node that would otherwise be invisible in html.
The problem for us is that when importing data from external sources there are lots of different scenarios where you might either want to replace all unicode newlines with
<br>s or use them to create separate paragraphs, or just remove them all together. But it’s virtually impossible to detect the intention just by looking at the data.
Maybe long term we can add a setting somewhere to customize the behavior, but that seems like a pretty big undertaking technically to improve the experience in the short term.
Would be interested in your thoughts on this as someone who’s been working around this behavior in the CMS.
My thinking is that the main pain point here is that it’s not intuitive that
white-space: pre-wrap; is being added or what the implications of it are, and unlike with clipboard/pasting from other apps there’s a little more control with things going into the CMS.
So we could improve the experience for now by converting all unicode newlines to line breaks. There will likely still be cases where you’d need to go in and manually tweak the imported rich content but at least the experience would be more consistent and predictable.