Re: [Lynx-dev] lynx misrenders many *IN*valid xhtml5 pages on my site

Lennart Jablonka dixit: > I see we are in agreement that > > is not /invalid/ due to omission of space before /> or due to self-closing It’s not a valid webpage. It’s an XML document, but not a webpage. > I read that

Re: [Lynx-dev] lynx misrenders many *IN*valid xhtml5 pages on my site

Quoth Thorsten Glaser: Handling XHTML approximately by treating it as HTML-syntax HTML may be useful in stead of refusing to handle XHTML, but that is not implementing XHTML. Yes, but the onus is on the *server* to provide the data in a format the client can handle because native XHTML-as-XML

Re: [Lynx-dev] lynx misrenders many *IN*valid xhtml5 pages on my site

Lennart Jablonka dixit: > Handling XHTML approximately by treating it as HTML-syntax HTML may be useful > in stead of refusing to handle XHTML, but that is not implementing XHTML. Yes, but the onus is on the *server* to provide the data in a format the client can handle because native

Re: [Lynx-dev] lynx misrenders many *IN*valid xhtml5 pages on my site

Quoth Thorsten Glaser: There’s HTML-compatible XHTML, which you can serve as text/html, and there’s nōn-HTML-compatible XHTML, which you must serve as application/xhtml+xml, yes and if you expect to serve websites you may serve the latter only if explicitly requested by the browser because

Re: [Lynx-dev] lynx misrenders many *IN*valid xhtml5 pages on my site

Lennart Jablonka dixit: >> Yes, but then it MUST send HTML-compatible things or it’s not >> an XHTML page. As simple as that. (I also serve my XHTML as >> text/html always and just write it in compatible mode.) > > I don’t buy this. What is and isn’t XHTML isn’t dependent on what the > client

Re: [Lynx-dev] lynx misrenders many *IN*valid xhtml5 pages on my site

Quoth Thorsten Glaser: Nope: HTTP_ACCEPT='text/html, text/plain, text/sgml, text/css, */*;q=0.01' Indeed. I was using an older version of lynx. It seems v2-9-0dev_0l regressed in dropping application/xhtml+xml from Accept. That’s a consequence of: --- a/src/HTInit.c +++

Re: [Lynx-dev] lynx misrenders many *IN*valid xhtml5 pages on my site

Hi again! Lennart, you nerdsniped me. Dixi quod… >Lennart Jablonka dixit: >>> I’m not sure whether it may then also self-close all tags but would >>> assume so (except I know tech is… tricky). >> >> As in an XML document, and are entirely equivalent, >> yes, >> the server may then

Re: [Lynx-dev] lynx misrenders many *IN*valid xhtml5 pages on my site

Lennart Jablonka dixit: > as is the case for lynx Nope: HTTP_ACCEPT='text/html, text/plain, text/sgml, text/css, */*;q=0.01' > Also, I’m under the impression that content > negotiation à la Accept is entirely optional—the server is free to ignore Yes, but then it MUST send HTML-compatible

Re: [Lynx-dev] lynx misrenders many *IN*valid xhtml5 pages on my site

Quoth Thorsten Glaser: Lennart Jablonka dixit: And here I thought that all of XHTML 1.0, XHTML 1.1, HTML5 XML syntax, and WHATWG HTML XML syntax defer parsing to the XML processor. As usual, it depends. Iff the browser requests XHTML served as XML, that is, if the browser sends an HTTP

Re: [Lynx-dev] lynx misrenders many *IN*valid xhtml5 pages on my site

Quoth Thorsten Glaser: Your file is well-formed XML, but neither valid for webbrowsers (due to the omission of the space before “/>” self-closing tags) nor actually valid for any XHTML DTD because you self-close tags that MUST NOT be self-closed. And here I thought that all of XHTML 1.0, XHTML

Re: [Lynx-dev] lynx misrenders many *IN*valid xhtml5 pages on my site

Lennart Jablonka dixit: > And here I thought that all of XHTML 1.0, XHTML 1.1, HTML5 XML syntax, and > WHATWG HTML XML syntax defer parsing to the XML processor. As usual, it depends. Iff the browser requests XHTML served as XML, that is, if the browser sends an HTTP Accept header that contains

Re: [Lynx-dev] lynx misrenders many *IN*valid xhtml5 pages on my site

Shlomi Fish dixit: >> > lynx >> > https://www.shlomifish.org/humour/Summerschool-at-the-NSA/ongoing-text.html >> > still misrenders. OK, I had a look at this now. Your file is well-formed XML, but neither valid for webbrowsers (due to the omission of the space before “/>” self-closing tags)