Proposal: valid XHTML for basic theme output. #12165
jayaddison
started this conversation in
Feature requests and ideas
Replies: 1 comment
-
Sounds reasonable to me 👍 I guess,from a"theoretical" perspective, I'm interested to know does anyone think there is ever a valid reason to have non-compliant XHTML? Or would we loosely ascribe this to "bugs" in these templates? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is your feature request related to a problem? Please describe.
It seems that most of the HTML output generated when building Sphinx's own documentation using the
basic
theme (not currently what we have configured) is XHTML-compliant - that is, it's also valid XML.In fact, of
146
HTML files,144
are valid XML. The only two exceptions currently are:search.html
anddomains.html
.search.html
, there is adefer
attribute that is not valid XML.domains.html
, there are unclosed<span>
tags that are not valid XML.I ran the following utility script to determine that, after using
sphinx-build -b html doc _build
to self-build the documentation -- with thehtml_theme
set tobasic
.Trimmed output:
Describe the solution you'd like
basic
theme -- in other words, fix the output forsearch.html
anddomains.html
.html5
builder tests -- to check some simple cases for valid XML.Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
I think this would enable us to drop permissive HTML parsers such as
html5lib
andlxml
from oursphinx[test]
dependencies.html5lib
in favor oflxml.html
#12157.Beta Was this translation helpful? Give feedback.
All reactions