[wp-trac] [WordPress Trac] #42972: XHTML CDATA compliance regression in preview script

[WordPress Trac]

#42972: XHTML CDATA compliance regression in preview script
--------------------------+------------------------
 Reporter:  sephr         |       Owner:
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:  4.9.1
 Severity:  normal        |  Resolution:  duplicate
 Keywords:                |     Focuses:
--------------------------+------------------------

Comment (by sephr):

 @dd32 I've been using XHTML(5) with my custom theme on WordPress since
 2007, and the codex still says that you support it (and has ever since I
 started using WordPress).

 If you wish to officially drop XHTML support, codex.wordpress.org needs to
 be revised. Here are some codex.wordpress.org links that suggest that
 XHTML is still supported by WordPress:

 > WordPress prints XHTML from all its internal functions
 ― https://codex.wordpress.org/HTML_to_XHTML#Why_Should_I_use_XHTML

 > improving XHTML compatibility (don't mess up people's code)
 ― https://codex.wordpress.org/Testing#Testing.2FJavascript_and_WYSIWYG
 (Implies that there was usage of XHTML and that WordPress developers
 should be mindful of compatibility)

 Some changelog entries with descriptions related to fixing XHTML
 compatibility:
 https://www.google.com/search?q=inurl%3Ahttps%3A%2F%2Fcodex.wordpress.org%2FChangelog%2F+XHTML

 I haven't had any issues with WP core XHTML support until recently the
 past couple years. The majority of my issues have been from components
 that I've been using for over a decade emitting proper XHTML that have
 been absorbed by Jetpack (e.g. WP Stats) and recently updated to emit
 malformed XHTML.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/42972#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform