[wp-meta] [Making WordPress.org] #8159: Trac pages claim XHTML, render as HTML5

[Making WordPress.org]

#8159: Trac pages claim XHTML, render as HTML5
-------------------------+-------------------------
 Reporter:  jonsurrell   |       Owner:  dd32
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Trac         |  Resolution:  maybelater
 Keywords:               |
-------------------------+-------------------------

Comment (by jonsurrell):

 Replying to [comment:4 dd32]:
 > You might be better off using the CSV or RSS trac options for whatever
 your parsing need is.

 I'm using the CSV for tickets, but haven't found a similar option for
 changesets (aside from reading the whole RSS, which isn't really suitable
 for a specific changeset lookup). I'd love to know if it exists!


 Replying to [comment:6 dd32]:
 > > Modify request headers to use Content-type:
 application/xhtml+xml;charset=utf-8. Chrome shows several errors on Trac
 changesets in this case.
 >
 > My historic knowledge says this will cause browsers to use a strict XML
 parser, rather than a vague HTML parser.

 Exactly, [https://www.w3.org/2010/04/xhtml10-strict.html the DOCTYPE is
 for XHTML 1.0] which is [https://www.w3.org/TR/xhtml1/#xhtml the XML
 flavor of HTML4]:

 > XHTML documents are XML conforming. As such, they are readily viewed,
 edited, and validated with standard XML tools.

 XHTML support in WordPress [https://core.trac.wordpress.org/ticket/64442
 is starting] to [https://core.trac.wordpress.org/ticket/59883 go away]. I
 researched this because I was concerned that changes coming in WordPress
 7.0 could break some Trac page. Fortunately the pages are served as HTML5
 so there's no issue.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/8159#comment:7>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org