The only part I don't get isn't even about the page in question:
> My first reaction was “why not just deliver something with Content-Type: text/plain; charset=utf-8 and dispense with the invalid code, but perhaps that’s just me overthinking the non-existent problem.
Yes, it's about the HTML-less plain text page https://no-ht.ml which is UTF-8 plain text which browsers should be able to render.
Does anyone here have deep knowledge, quotes from grimoires, or relevant strange tales?
I tested with a bunch of browsers on mobile and desktop - some browsers forced a download of plain text and / or wouldn't render the characters properly.
Some browsers assume the server is lying and think they know best.
> My first reaction was “why not just deliver something with Content-Type: text/plain; charset=utf-8 and dispense with the invalid code, but perhaps that’s just me overthinking the non-existent problem.
Yes, it's about the HTML-less plain text page https://no-ht.ml which is UTF-8 plain text which browsers should be able to render.
Does anyone here have deep knowledge, quotes from grimoires, or relevant strange tales?