content/notes/on-valid-xhtml5-again.md

@@ -1,16 +0,0 @@
----
-title: "On valid XHTML5 again"
-date: 2024-06-23T16:15:06-04:00
-replyURI: "https://snug.moe/notes/9uv9x9r9tqq1pcxu"
-replyTitle: "what if I put in a bunch of effort to make my website valid XHTML5"
-replyType: "SocialMediaPosting"
-replyAuthor: "LunarEclipse"
-replyAuthorURI: "https://lunareclipse.zone/"
-syndicatedCopies:
-    - title: 'The Fediverse'
-      url: 'https://pleroma.envs.net/objects/4660408b-41dc-4850-9197-9ce6585fceb7'
----
-
-Switching a site to XHTML5 is only a lot of work at first, because it may have latent bugs. For instance, you may have a stray tag that the HTML parser auto-closes but an XHTML parser won't. I find this effort worthwhile because [some of these bugs will eventually visibly manifest]({{<relref "/notes/polygot-xhtml5.md">}}).
-
-One thing I've noticed is that some tools are incompatible with an XHTML5 MIME type. Site auditors like Lighthouse are only provisionally compatible, and some browser extensions are rather buggy. You can compare them yourself on seirdy.one: switch the MIME type by appending `/index.xhtml` to a URL. You may have to disable the CSP sandbox by [appending `?sandbox=off` to the URL]({{<relref "/meta/csp-bug-reproduction.md#how-to-use-this-page">}}) to get Lighthouse to work. I keep my site polygot and serve with the `text/html` MIME type by default for maximum compatibility.

content/notes/progressive-enhancement-class-feedback.md

@@ -1,20 +0,0 @@
----
-title: "Progressive enhancement class feedback"
-date: 2024-06-23T15:46:01-04:00
-replyURI: "https://dillo-browser.github.io/pec/"
-replyTitle: "Progressive Enhancement Class"
-replyType: "WebSite"
-replyAuthor: "Dillo browser"
-replyAuthorURI: "https://dillo-browser.github.io/"
-syndicatedCopies:
-    - title: 'The Fediverse'
-      url: 'https://pleroma.envs.net/objects/c04df0f6-a868-4af6-91b6-ce6e5b76c399'
----
-
-[This page at the time of writing](https://web.archive.org/web/20240623192730/https://dillo-browser.github.io/pec/) grades websites' progressive enhancement based on their ability to work without JavaScript. Everything, not just JavaScript, should be progressive enhancements.
-
-HTML elements already have progressive enhancement built-in. CSS, JS, and embedded content should be progressively enhanced too. The page should make sense without scripts and styles, alt-text should be available in the absence of embedded media, etc. We shouldn't put scripting on a pedestal above everything else.
-
-I suggest replacing references to JavaScript with references to non-HTML content. See also: ["curlable" on the IndieWeb wiki](https://indieweb.org/curlable).
-
-A more minor piece of feedback: I'd suggest re-sizing the badges to 88-by-31 pixels if possible. It's a very popular size for badges; at these dimensions, they would look good alongside others of the same size ([examples from the W3C](https://www.w3.org/QA/Tools/Icons)).