You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AFAIK, the content type "text/xhtml" is not standard, even if the W3 validator doesn't complain. It was included in one of the first drafts of the XHTML 1.0 specification in February of 1999, but a concern was raised to add a new media type, and later removed in May, finally ending in "text/html" or "application/xhtml+xml", see:
The meta tag is a difficult problem, but in https://www.w3.org/TR/xhtml-media-types/#media-types there us no mention of text/xhtml at all so it looks like it would be better to use application/xhtml+xml.
I don't know whether this will have some side effects though.
The XHTML 1.0 documents generated by Doxygen include a
<meta>
tag that overrides the content type to "text/xhtml":Generated from here:
https://github.com/doxygen/doxygen/blame/78422d3905e57acebf0374feefafa6578dbe86aa/templates/html/header.html#L4
AFAIK, the content type "text/xhtml" is not standard, even if the W3 validator doesn't complain. It was included in one of the first drafts of the XHTML 1.0 specification in February of 1999, but a concern was raised to add a new media type, and later removed in May, finally ending in "text/html" or "application/xhtml+xml", see:
https://www.w3.org/TR/xhtml-media-types/
https://www.w3.org/TR/xhtml1/#C_9
This problem was observed when fixing a similar problem in the Dillo browser, which has a workaround to handle the "text/xhtml" content for Doxygen.
Here is the patch:
The text was updated successfully, but these errors were encountered: