Editing header-fields vs. headers in Text-field

[pxamike]

The screenshot shows a content elements of type Text. The first header is in the Header-field, the second header is in the Text-field.

In frontend-editing (tested in 1.3.0), the div with contenteditable appears after the h1-tag instead of inside. The effect of this is that it's not really clear that it's a header that you are editing.

[mabolek]

@pxamike If I understand you correctly, this isn't a bug.

Technically, a rich text field can contain anything. Best practice would be to leave headers out of the rich text field.

I'm marking this as something we should add to the documentation. Integrators should maybe consider disabling headers in rich text fields.

[erredeco]

I have the same issue on 1.9.0 and honestly, it is a bug and not a documentation problem: It happens when you have a textarea in your content element (like the plain TYPO3 "Text"), it changes the appearance of the page and, worst, it makes impossible for example to edit the whole content element itself.
It happens also with "Header" content element.
It happens also with "Table" content element
It does not seem to happen with "Text and Images" content element

[Messj1]

@mabolek I think you didn't understand correctly.

@pxamike If I understand you correctly, this isn't a bug.

Technically, a rich text field can contain anything. Best practice would be to leave headers out of the rich text field.

I'm marking this as something we should add to the documentation. Integrators should maybe consider disabling headers in rich text fields.

And the screenshot shows definitely that the h1 content was on a wrong place and the class was not proper set:

<div data-field="bodytext" ...>
  <div>
    <h1 class>...</h1>
    <div data-field="header" ...><!-- h1 content (content header) --></div>
    <div data-field="bodytext" ...>
      ...
    </div>
  </div>
</div>

But the configuration was wrong as i can see on the first data-field parameter.