Bug #99168
closedEpic #99669: CKEditor5 Collection
ckeditor turns trailing space into at the end of headlines, paragraphs and list items on save with Chrome, deletes that space with Firefox
0%
Description
Bug?
My first issue ever opened, hope it's correct.
Reproduced behaviour on a clean Typo3 Composer installation, without provider extension, backend only, in Chrome incognito window:
- created a page in the backend, on that page i create a Text element
- inside the ckeditor richtext field of the Text element i create a h2 with a space at the end
- save the Text element
- The heading above the text element now reads: Edit Page Content "This a h2 " on page ...
Firefox deletes that extra space when saving the Text element.
Safari acts like Chrome.
I found no related information on what should happen but at least one of the browsers might do it wrong?
Is found no rule saying to not put trailing spaces at the end of headlines or paragraphs or list-items (the above applies to all these cases).
Might this ' ' that came into existence this way show up in e.g. search engine results, too?
Updated by Frank no-lastname-given almost 2 years ago
The tracker texteditor transfomred the
, sorry
Above should read:
The heading above the text element now reads: Edit Page Content "This a h2 " on page ...
and:
Might this ' ' that came into existence this way show up in e.g. search engine results, too?
Updated by Georg Ringer almost 2 years ago
- Status changed from New to Accepted
this is also valid for v12 but this is a ckeditor issue. I opened https://github.com/ckeditor/ckeditor5/issues/12922 therefore
Updated by Andreas Kienast over 1 year ago
- Status changed from Accepted to Rejected
I honestly fail to see a reason why having &
nbsp;
is bad. Those characters are the result of having spaces at the end of your input, ensuring those are displayed as "intended" in the frontend. One could argue that browsers behave differently, which is apparently not the case in CKEditor 5 (TYPO3 v12, tested with Chrome and Firefox).
I assume this can be fixed in CKEditor only. However, CKEditor 4 (used until TYPO3 v11) is in LTS until 2023, whatever this means.
I tend to close this issue as, as stated, doesn't sound valid and I don't think CKEditor will change this in any case.