First of all, "not HTML5 compliant" is too strong for the quicksearch plugin – its code is valid in HTML5, but it doesn't use the new "search" input type like the built-in search form. Obviously, this is not an issue since the built-in search form works fine and suppresses the quicksearch plugin in sidebars.garvinhicking wrote:Once you find the exact problem, drop a note* The comment switch [theaded|linear] produces invalid HTML5. I'm not exactly sure what it is exactly.
* The quicksearch plugin's code is also not HTML5 compliant.
As for the comment switch, testing it with my local dev blog, the w3c validator gives me:
Since said URL doesn't have any spaces, it has to be NFC representation:Bad value /serendipity/index.php?url=archives/16-Podcasting-Video.html&serendipity[cview]=linear#comments for attribute href on element a: Illegal character in query component.
Syntax of IRI reference:
Any URL. For example: /hello, #canvas, or http://example.org/. Characters should be represented in NFC and spaces should be escaped as %20.
I assume this relates to one of the special characters in the URL, meaning #, ?, & or the square brackets …For various reasons, Unicode sometimes has multiple representations of the same character.
YL