TYPO3 Core

Do you happen to pass the menu code through lib.parseFunc(_RTE), e.g. due to <f:format.html/> instead of <f:format.raw/> in your template?

duplicate, I guess #65234

Mathias Brodala wrote:

Do you happen to pass the menu code through lib.parseFunc(_RTE), e.g. due to <f:format.html/> instead of <f:format.raw/> in your template?

Indeed! the empty tags are not be rendered in <f:format:raw> - but why?

Because <f:format.raw/> simply disables the HTML escaping applied by default in Fluid. OTOH <f:format.html/> by default passes its content through lib.parseFunc which by default puts paragraphs around empty lines by default since they are stored like this when editing via RTE.

Can we assume this is fixed for you?

I don't think that the problem can be considered fixed; But I would close this as duplicate of #65234

Well, it is fixed if you use the correct viewhelper depending on the input. For user input possibly created via RTE use <f:format.html/>, for code generated e.g. by TypoScript use <f:format.raw/>. That's how it has always been and is not a bug. ;-)

@mathias pardon me if I disagree, but I think that this issue is only about the output of the RTE, and the issue is about a wrong behavior of lib.parseFunc; this IMO, of course.

The RTE must not be involved here at all, it's simply that <f:format.html/> uses its lib.parseFunc_RTE. And lib.parseFunc_RTE behaves correctly since paragraphs are not stored in the database thus must be wrapped on output.

It could be argued whether <f:format.html/> should use lib.parseFunc by default instead but that would mean a breaking change.

Now that I tried to reproduce it using a Typoscript menu I understand what happens:
My test (latest 8.2-dev master):

1) create a TS menu:

lib.mainmenu=HMENU
lib.mainmenu{

 1=TMENU
 1.wrap = <ul>|</ul>
 1.NO = 1
 1.NO.wrapItemAndSub = <li>|</li>
 1.expAll =1
 2 < .1
 3 < .2
 4 < .3
}

<f:format.html>
<f:cObject typoscriptObjectPath="lib.mainmenu"/>    
</f:format.html>

3) Result: there are some empty

<p>&nbsp;</p>
<p>&nbsp;</p>

<f:format.html>

</f:format.html>

<f:format.html><f:cObject typoscriptObjectPath="lib.mainmenu"/></f:format.html>

I think it can be safely closed now.

[update] on my previous comment I have not considered the case "fluid styled content".
Test with 7.6.6:

1) create a FSC "Text with media" and put in the text a nested list like:

<ul><li>Arrivederci<ul><li>ciao</li><li>ciao</li></ul></li><li>ciao</li></ul>
<p>&nbsp;</p>

2) result on frontend: the empty p is duplicated because the Partial Textmedia.html has:

<f:format.html>{data.bodytext}</f:format.html>

Is there any solution or work around?
Have the same problem with p-tags on 7.6.10 :(

In 6.2 <f:format.html parseFuncTSPath=""> did the trick for me.

We faced a very similar issue where between all <p> tags with content there was some empty <p> tag added. E.g.

Text in RTE

Lorem

ipsum

Text in RTE (HTML view)

<p>Lorem</p>

<p>ipsum</p>

Frontend rendering

<p>Lorem</p>
<p>&npsp;</p>
<p>ipsum</p>

The problem was that we set RTE.default.proc.overruleMode = ts_css in our TS Config, setting it back to default resolved the issue (RTE.default.proc.overruleMode = default). In my opinion the dealing with line breaks in RteHtmlParser (e.g. streamlineLineBreaksForProcessing) is extremely error prone and should probably be simplified.