4 ms·
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
by msla 4y ago
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 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?
- edent 4y agoI wrote about it at https://shkspr.mobi/blog/2022/12/you-dont-need-html/ https://shkspr.mobi/blog/2022/12/you-dont-need-html/ 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.
- conaclos 4y agoThanks for the post :) I am wondering: why do you use the obsolete <plaintext> instead of <pre>? Why do you use the `ml` extension? By the way, I noticed some issues in the page: - trailing whitespaces - mixed of spaces/tabs - some wide characters such as ▽ seems to create aligning issues
- edent 4y ago> why do you use the obsolete <plaintext> instead of <pre>? Because it is funny. > Why do you use the `ml` extension? Because it is funny. Also, it was free. > By the way, I noticed some issues in the page: The source is open. Feel free to correct those issues.