Task #66631
closed
Why does Typo3 clean XHTML
0%
Description
Since Typo3 v7 the option "config.xhtml_cleaning" is secretely outdated and just compatibility. Do the developers dream of a world without clean codes. Even the inclusion of CSS files does not work without correction (single tag without ending backslash). If you want keep Typo3 usable there should minimum be a core extension including this ferature also in the feature.
Not everybody is ready to giver up clean code for the modern rubbish of the Google-Microsoft-and-Consorts-Consuming-Terror-Maffia
Updated by Christian Kuhn about 9 years ago
Hey anybody no-lastname-given,
there were tons of reasons to move this feature to compatibility6 extension:
- It is slow and could easily take more than 100ms for a single page
- It was only possible to parse xhtml (not html5) which is seldom used nowadays
- It created false positives, destroyed correct html, so it could easily do more harm than good
- The integration was ugly
- It was never thought to correct stuff from user input like from RTE. Instead, please configure your RTE correctly to remove crappy HTML if copy/pasted from word for example - decent RTE versions can do that pretty well nowadays
This feature will not be re-integrated into the standard CMS core for version 7 and above.
If you still insist on having this feature, please feel free to extract/copy the according code from compatibility6 and upload it as extension to TER. There are hooks in place (the moved code in compatibility6 use them already), so it should be easily possible to do that.
This issue will be closed as rejected now.