WordPress strips multiple line breaks inside of <pre> tags

[Viper007Bond]

Write a post:

<pre>
This


is




a
test.
</pre>

You end up with this:

<pre>
This

is

a
test.
</pre>

Probably related to wpautop() I imagine.

[azaozz]

(In [16394]) Remove invalid parent paragraph when pasting in the visual editor or switching visual to HTML and back, keep multiple empty lines in a <pre> tag, fixes #15095 fixes #15367

[Viper007Bond]

This isn't a TinyMCE issue, it's an output filter issue.

[azaozz]

Replying to Viper007Bond:
The same was happening when switching editors, perhaps we can apply the changes from the JS version of wpautop to the php one.

[Viper007Bond]

No I mean this isn't an editor issue. If I write the above example in the HTML editor, it stays exactly like that. I save the post, still correct. When I view it on the front end however, the extra line breaks are stripped out.

[Viper007Bond]

Whoops, I need to learn to read. Yes, we need to apply the code to the PHP-based `wpautp()~ too.

[Viper007Bond]

I also need to learn to spell apparently...

[westi]

Nah you can spell apparently fairly well it's the other words you should practice ;-)

[SergeyBiryukov]

Related: #18534

[TomAuger]

Modified wpautop in formatting.php

[TomAuger]

My approach was to preserve all content inside <pre> tags from most of the substitution that occurs on the rest of the text. As a result, the call to clean_pre() is no longer necessary.

[SergeyBiryukov]

Closed #19666 as a duplicate.

[MikeHansenMe]

This problem still exists but the patch would not apply. Needs Refresh.

[MikeHansenMe]

In addition to my last comment the problem still exist when switching between Visual and Text mode. If you paste the example in text mode and click publish then reload the page it remains as it should. It seems a similar fix is needed for the js.

[nacin]

I can't seem to reproduce this. This needs a unit test, then maybe we can figure out exactly what (PHP/JS/TinyMCE) needs changing.

[azaozz]

This was fixed (together with another <pre> issue) in [20307], see #19855. The approach is similar to the patch here.