Jeroen Wiert Pluimers @wiert@mastodon.social Profile picture
Makes things work in .NET/Win32/x64/C#/SQL/Delphi. Surviving rectal cancer. Married a cancer survivor. Responsible for brother with IQᐸ50. @AdestMusica member.

Feb 8, 2022, 6 tweets

@S_2K I thought it would be something like explained in stackoverflow.com/questions/1643…

But it is yet another html oddity where structural and logical concept are mixed in one language.

@S_2K BTW: Thanks for teaching me about that NU validator.

As a result I took a look at the Wayback machines saves of it at web.archive.org/web/*/https://…*

This shows it accepts a ?doc= parameter

1/

@S_2K With that you can dynamically load a web-page, for instance validator.w3.org/nu/?doc=https:…

2/

@S_2K Of course I tried it with the HTML page form your gist: validator.w3.org/nu/?doc=https:…

Bummer:

<<IO Error: Non-XML Content-Type: text/plain.>>

That is caused by GitHub always serving RAW files as text/plain.

3/

@S_2K But wait, we can fix that with raw githack:

It turns your gist HTML file into an actual web page at gist.githack.com/s2k/8e54698e01…

It gets serviced with this header:

<<content-type: text/html; charset=utf-8>>

4/

@S_2K Which means you can directly run the W3 NU HTML validator on it:

validator.w3.org/nu/?doc=https:…

How cool is that: it works!

Quickly it shows you "Error: No p element in scope but a p end tag seen.", just what you started the thread with (:

5/5

Share this Scrolly Tale with your friends.

A Scrolly Tale is a new way to read Twitter threads with a more visually immersive experience.
Discover more beautiful Scrolly Tales like this.

Keep scrolling