---
title: "Breaking: #79273 - Removed RteHtmlParser proc options"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:breaking-79273"
source: "Changelog/8.6/Breaking-79273-RemovedRteHtmlParserProcOptions.rst"
typo3-version: "8.6"
typo3-major: 8
type: "breaking"
issue: 79273
forge: "https://forge.typo3.org/issues/79273"
tags: ["RTE", "TSConfig"]
rendered: "2026-09-18T17:00:34+00:00"
---

# Breaking: #79273 - Removed RteHtmlParser proc options {#breaking-79273}

See [forge#79273](https://forge.typo3.org/issues/79273)

## Description {#description}

The following TSconfig options for processing content of RTE fields have been removed:

-   `RTE.default.proc.dontConvBRtoParagraph`
-   `RTE.default.proc.dontProtectUnknownTags_rte`
-   `RTE.default.proc.dontConvAmpInNBSP_rte`

## Impact {#impact}

Setting any of these options has no effect anymore.

Content coming from the database towards the RTE will now always keep unknown tags (but HSC'ed), and never have any
double-encoded ` ` characters - this was a default since a decade already.

Content stored in the database will now always treat `<br>` tags as intentional and not treat them like paragraphs, a behaviour which
is common in modern Rich Text Editors.

## Affected Installations {#affected-installations}

Installations explicitly setting `RTE.default.proc.dontConvBRtoParagraph = 0`, `RTE.default.proc.dontProtectUnknownTags_rte = 1` or
`RTE.default.proc.dontConvAmpInNBSP_rte = 1` might experience different results when editing and saving content via an RTE.

## Migration {#migration}

Remove the TSconfig options, as they have no effect anymore. Any custom implementation which is necessary should be handled
via separate entryHtmlParser and exitHtmlParsers in both directions.