Bug #100046
closedCreating a link within an RTE CKEditor table cell without having any text selected merges this table cell with a neighboring cell
0%
Description
Using
fluid_styled_content v11.5.24
rte_ckeditor v11.5.24
When editing a content element with CKEditor, when adding a link within an HTML table cell ( <td>
) WITHOUT having selected some text on which this link is being added to, this table cell gets merged with a neighboring cell, effectively deleting one <td>..</td>
element.
bodytext
before link insertion:
<table border="1">
<tbody>
<tr>
<td>111</td>
<td>222</td>
<td>333</td>
</tr>
<tr>
<td>444</td>
<td>555</td>
<td>666</td>
</tr>
<tr>
<td>777</td>
<td>888</td>
<td>999</td>
</tr>
</tbody>
</table>
bodytext
after link insertion:
<table border="1">
<tbody>
<tr>
<td>111</td>
<td>222</td>
<td>333</td>
</tr>
<tr>
<td>444<a href="mailto:foo@example.com">555</a></td>
<td>666</td>
</tr>
<tr>
<td>777</td>
<td>888</td>
<td>999</td>
</tr>
</tbody>
</table>
Here is a screen recording:
Maybe this was introduced with the fix for https://forge.typo3.org/issues/92245 (CKEditor: Table wrapped around links when linking a text in a table (Chrome))?
Files
Updated by Gerrit Hübbers over 1 year ago
This bug is not reproducible in standalone CKEditor 4 (TYPO3 11's CKEditor IMHO is based on CKEditor in Version 4):
https://ckeditor.com/ckeditor-4/demo/
With standalone CKEditor 4, when creating a link without having any text selected, the link will get as its text content the actual URL as text, and <td>
cells are not merged/deleted.
Hence in my opinion, the bug reported here originates from TYPO3's CKEditor integration.
Updated by Georg Ringer over 1 year ago
- Related to Bug #92245: CKEditor: Table wrapped around links when linking a text in a table (Chrome) added
Updated by Riccardo De Contardi 4 months ago
This is reproducible only on TYPO3 11.5.35, not on 12.4.14 nor on 13.2.0-dev
Updated by Riccardo De Contardi about 2 months ago
- Status changed from New to Closed
I close this issue as it seems to affect just version 11.
If you think that this is the wrong decision or experience the issue again on v.12 or higher please open a new issue with a reference to this one. Thank you.