TYPO3 Core

Sorry, I made on the same day a full rollback to v7.6 because a clean XHTML output has absolute priority. Especially I did not like the perspective to repair many hundreds of content element - many of them with sophisticated semantic tagging.

Also I do not understand what the RTEs have to do with this problem because rtehtmlarea is not installed and the new one is not activated. I use the standard "Text & Media" type of fluid_styled_content from Typo3 v7.6 but without rich text editor because I want clean XHTML and not any editor rubbish. In v7.6 it was working without any problems but v8.7 seems to have problems with some standard (X)HTML tags like <abbr>.

Nearly, there are two cases:

A
In Text & Media elements migrated from v7.6 the former <abbr> tags are coded

<abbr>

<abbr>

B
When I create a new content element or edit a old content element, all new written opening and closing <abbr> tags are not saved.

I think - together with some related problems - the problem of v8 is that in all the euphory for the new RTE also the core system of Typo3 was optimized just for it without checking whether it works also in the hard core way without any RTE.

Hi,

thanks for your report and you're right - we've simplified the RTE processing configuration and did not provide proper defaults when no RTE is available.

Two solutions:
a) create a 'default' RTE configuration.yaml like in EXT:rte_ckeditor (register in ext_localconf.php of your own extension) and use the EXT:rte_ckeditor/Configuration/Rte/Processing.yaml as template.
b) Add this PageTSconfig option RTE.default.proc.allowTags := addToList(abbr)

We'll also create a patch to fix this in the next v8 version.

Patch set 1 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/58749