- Issue created by @karlshea
- Status changed to Postponed
almost 2 years ago 7:04pm 8 February 2023 - ๐ง๐ชBelgium wim leers Ghent ๐ง๐ช๐ช๐บ
This is a borderline data loss case. ๐ฌ
Thank you for finding the upstream bug report and for reporting your findings there too! ๐ I have a meeting with the CKEditor 5 team tomorrow and will raise this there.
- ๐ง๐ชBelgium wim leers Ghent ๐ง๐ช๐ช๐บ
Discussed this with @Reinmar from CKEditor 5!
This bug has also been frequently reported by other CKEditor 5 users; it's already scheduled to be fixed in the coming months! ๐
- ๐ต๐ฑPoland Reinmar Warsaw, Poland
Wim Leers โ credited Reinmar โ .
- ๐ง๐ชBelgium wim leers Ghent ๐ง๐ช๐ช๐บ
Good news from @Reinmar!
https://github.com/ckeditor/ckeditor5/issues/3172 landed, which superseded https://github.com/ckeditor/ckeditor5/issues/11536 ๐
That means the next CKEditor 5 update will fix this ๐
- ๐บ๐ธUnited States karlshea Minneapolis ๐บ๐ธ
I don't believe that PR will fix most of these issues, and I think the reason for that is shown in the test from that PR that shows their expected data model:
'<table headingRows="1">' + '<tableRow>' + '<tableCell><paragraph>Date</paragraph></tableCell>' + '<tableCell><paragraph>Event</paragraph></tableCell>' + '<tableCell><paragraph>Venue</paragraph></tableCell>' + '</tableRow>' +
They don't seem to be able to represent an arbitrary table structure within the editor, only rows and cells with the number of headings as attributes on the table container. So most of my examples above cannot be input into Drupal without using an input format that doesn't use CKEditor at all.
Issue 13609 might be a better one to track for this Drupal issue, but until they change their data model to match what you can do with a real table CKEditor can't be used on input formats where your editors may need to add complicated tables.
- ๐ง๐ชBelgium wim leers Ghent ๐ง๐ช๐ช๐บ
Just discussed with @Reinmar & Witek. Witek says 2 of the 3 problems surfaced in the issue summary are 100% fixed, and the third is no longer a data loss bug but just a semantics loss bug: a
<th>
may get converted to a<td>
, which is far less severe.(Or at least that's what I think I understood, my not having a working dev environment right now made this more complicated to follow ๐ )
So actually this issue is currently critical data loss (clarifying in metadata), but after the next release should become "major data loss" (because semantics loss).
I'd still like @KarlShea to confirm though ๐ ๐
- Status changed to Fixed
over 1 year ago 8:58am 26 April 2023 - ๐ง๐ชBelgium wim leers Ghent ๐ง๐ช๐ช๐บ
See @smustgrave's report at #3355358-8: Update CKEditor 5 to 37.1.0 โ . He was able to confirm what I wrote in #11, that there definitely is no longer a data loss bug. ๐
I'm going to mark this issue as fixed. @KarlShea, if you have additional edge cases relating to table handling in CKEditor 5, could you please create a new issue? ๐
Automatically closed - issue fixed for 2 weeks with no activity.
- Status changed to Fixed
10 months ago 4:44pm 1 February 2024 - ๐บ๐ธUnited States j. ayen green
Was a separate issue forked from this for the semantics loss? I understand that semantics is less critical than data, but try to tell editors that their tables getting munged because CKEditor cannot handle th vs td.
- ๐บ๐ธUnited States karlshea Minneapolis ๐บ๐ธ
No, it's been brought up multiple times on both Slack and in the CKEditor issue queue and no one seems very concerned.