Closed eklausme closed 1 year ago
Yeah, none of these cause any issues, but for brevity I've gone and sorted them all out. All the non-closing tags are up to HTML 5 standard, I've moved Clacks Overhead to middleware, and sorted out the rest of the info and warnings.
One issue is the <content>
tag. I've made a note to replace this with <section>
but will need to programatically update all users' custom styling just in-case they use <content>
as a selector.
Not a big issue in any way, but hopefully worth noting.
Checking Herman's blog with Nu HTML Checker shows some errors like:
or
or
There are also a couple of info-messages, like
The error regarding
X-Clacks-Overhead
obviously can be ignored, as this seems to be intentional.For bearblog.dev there is
and
There are other errors in the validator report.
Just for completeness: The mentioned blogs show just fine on Firefox and Chromium. So errors in the validator do not necessarily lead to problems in actual browsers. But usually, for a new blog, you aim to be "validator-compliant".
Thanks for providing bearblog.dev.