Hi @dan,
hope I do not loose track on what I wrote already. But the textArea prop allows newlines, but those wont get rendered automatically. Has to be converted with a regex to <br> or using a <pre> wrapper. Might be something good in the documentation to add.
As usual makes sense.
They should be… did you type in the text or paste it? There’s currently a bug with pasted text not respecting the carriage returns.
If this was fixed, nothing would be need to be documented…right?
I dont mean the textArea in the editor. But the textArea in the properties.
As I mentioned it makes sense, since a \n does not get rendered in html.
But some people might stumble over this.
A multiline text only at code, not at rendering.
This could be a bug—we’ll need to take a closer look to see exactly what’s going on.
That said, I wanted to jump in and emphasize that we’re aiming to keep text editing inline as much as possible. I’m not entirely sure what you’re building here, and there are certainly cases where using a textarea in the component’s property controls makes sense. However, whenever possible, we recommend using an inline @text() so users can edit text directly on the page 
I used that component for the link list. And use the textArea in a collection.
Other then that I am with you. Since @text() and so on does not support dynamic ids as I remember I am not sure how I would achieve that.
@bon … but as I mentioned It makes sense. If you auto generate <br> on the textArea you wont be able to use it for other stuff.
