HA! Offline short blog post from mollydotcom years and @WHATWG #HTML5 round one. Quipped to Honey kitty "FLASHback to HTML5 FTW!" Got a kitty butt in response. Apparently, not a pardonable pun. At all. But... this? Anyone write and serve 'XHTML5'... like, EVER? See next 2 tweets.
1
1
Tuesday 14 July 2009 HTML5 & XHTML5: MIME is The Answer --- Currently, all the HTML5 / XML “serialization” stuff simply boils down to two straight-forward rules: If HTML5 using HTML syntax is served with MIME type text/html This is HTML serialization. [continued >]
1
..If HTML5 using XML syntax is served with MIME type application/xhtml+xml then this is XML. Disclaimer on all things series 5: I might be wrong now. Then again, I might be right in five minutes. ---end post--- So did anyone? EVER? I did do up a code sample. In Word. For print!
1
I wanted to use it back in the day, but it was just too cumbersome. And it did not have any advantages in practice. And then when ARIA came around with attributes just not present in HTML5 you would need to properly specify your namespaces, and that was the end of that 😂
1
1
Replying to @yatil
LOL! All true and we had a certain browser implementation problem too. I was in the WG fascinated by href attribute module and the concept of href any element when we got flushed. I wanted the option of XML rigor and extensibility evolved along with, not replaced by... ;-)

Apr 22, 2021 · 9:44 AM UTC

1
Replying to @mholzschlag
I still wish we could HREF all the things, the lengths we have to go to make it remotely work (not even talking about making it accessible) is ridiculous. Ah, well, it is now WHATWG all the way down… 🤷‍♂️
1
1
It's the one size fits none problem. Why humans are so stuck on the one way is the only way b.s. confounds me. It's extreme exclusion not imaginative inclusion driven ideologically, not pragmatically. Human fail point across any discipline I can imagine. Monoculture != innovation
1