wpautop inserts line break elements in select element breaking XHTML 1.1 Strict compatibility

[akerem]

The wpautop function of Wordpress inserts line break elements (<br />) after option elements in a select element of a form, breaking XHTML 1.1 Strict compatibility.

The problem can be solved simply by adding option to $allblocks variable in formatting.php

A diff file is attached.

[akerem]

Diff file for formatting.php

[dd32]

Confirmed bug in trunk:

$in = "<select>
<option>Value</option>
</select>";

$out  = wpautop($in);

var_dump($out);

?> 
string '<select>
<option>Value</option><br />
</select>
' (length=48)

Results after:

string '<select>
<option>Value</option>
</select>
' (length=48)

Note: If anyone is confused, that patch is reversed, Its the addition of option, not the removal.. had me perplexed for a moment there.

[dd32]

(In [13903]) Dont pee on <option>. Prevents the addition of a <br/> following a </option>. Props akerem. Fixes #11947

[WraithKenny]

(Tested on 3.3-aortic-dissection)

The PHP version is fixed, but not the JavaScript version (Everyone always forgets the poor JavaScript version). Try in HTML Tab:

<select>
	<option>Value</option>
	<option>Value</option>   
	<option>Value</option>
	<option>Value</option> 
	<option>Value</option> 
</select>

Then switch to Visual and Back. The result is:

<select> <option>Value</option></select>
<select> <option>Value</option></select>
<select> <option>Value</option></select>
<select> <option>Value</option></select>
<select> <option>Value</option></select>

There are other fixes (I'm sure) that got applied to the php wpautop, but not the JavaScript version. Sadly, TinyMCE's reputation might be taking a beating over stuff like this ;-)

[WraithKenny]

related #18514

[SergeyBiryukov]

Replying to WraithKenny:

The PHP version is fixed, but not the JavaScript version

In 11947.patch​ I've synchronized block tags between formatting.php and editor.dev.js, which fixes the issue with <select>.

Isn't it better to open a new ticket for it though? I was under impression that tickets from a completed milestone generally shouldn't be reopened.

[SergeyBiryukov]

Opened #18534 for synchronizing block tags.

Closing as fixed for 3.0.