3.3.1: Visual editor saves a line break in a table cell so the text renders in the wrong column

[andy-vdg]

Version: 3.3.1 (Docker), PostgreSQL; markdown editor settings default (multimdTable on)

What happens

In the Visual editor, a line break inside a table cell (Shift+Enter) is saved as a backslash and a newline inside the pipe row. The rendered page then puts the text in the wrong cell: the renderer reads the trailing backslash as a MultiMarkdown multi-line row, so the text after the break is moved into the first column.

Steps

1. Create a page with the Visual editor and insert a 2×2 table.
2. In the first body row, type Street 1, press Shift+Enter, type City.
3. Add a second body row, then save.

Saved markdown (from the page source):

| **Name** | **Address** |
| --- | --- |
| Anna | Street 1\
City |
| Ben | Street 2 |

Rendered HTML:

<tr><td><p>Anna<br>City</p></td><td><p>Street 1</p></td></tr>
<tr><td>Ben</td><td>Street 2</td></tr>

City now sits under Name instead of Address. On a real page with several multi-line cells, some rows also dropped out of the table.

Expected: the break survives in the cell, for example as <br>. A cell written by hand as Street 1<br>City renders correctly, but the Visual editor shows that <br> as a raw inline chip rather than as a line break.

Where it seems to come from: the table serializer renders each cell with renderInline, and a hard_break is written as \ plus a newline. A pipe table cannot contain a newline.

[NGPixel]

Fixed via 2b2ee7c. Will land in next release.