I’ll try it, but I can’t bear to tell my app user’s for such a kludgy workaround! It’s like telling them only to only drive backwards to get to work. It’s a user form: they’d say “why?”
I wouldn’t call it a bug. It’s the nature of how HTML works and has always worked since the beginning of the internet. It’s always been something to be aware of when working with HTML, because by nature it will eliminate any extra spaces.
One thing you could consider doing is create a Template column to wrap the content with PRE tags, which will display the text in a fixed width font, but will preserve spaced and line breaks as written. Like this: <pre>{content}</pre>
Another thing you could try doing is set up a template column that replaces carriage returns with
or tags so the user does ha e to do anything special.
I’m confused. My CRLF work fine throughout the body of the text. Only the last line doesn’t wrap (sorry if my screen shots weren’t separated to make this clearer - top was input, bottom was output). That’s why I thought it was Glide and not a general HTML issue.
I guess I could use a calculated field to replace the last CRLF with something that works…?
Edit: I suddenly thought - is it because the last para has a comma, then CRLF, then last para? Is the rich text or HTML treating that last para differently because it ends with a comma (guess I could test easily enough!)