On 3/15/26 6:43 AM, Stephen Paul Weber wrote: (quoting Marvin...)
Now specifically about XHTML, it's important to note that XHTML 1.0/1.1 were retired at its standardization body (W3C) in 2018. [1] The XML- serialization of HTML5 is not recommended (see big warning on [2]). New rendering engines like Servo do not support XHTML.
Side point: As a former Mozillian, I will say that Servo is not really new (development started in 2012) and even 14 years later it's pretty much just an experiment. Building a complete browser is a Herculean task and I doubt that Servo will ever provide the engine for such a beast.
The warnings about XML serialization hardly seem relevant to an XML napive contuxt such as ourselves.
Main point: I was convinced to advocate for deprecating XHTML-IM by Waqas Hussain, who found serious security vulnerabilities in the wild among a number of XMPP clients. Although in theory XHTML-IM might be "nice", as Sergei put it in this thread (and I was always quite fond of it myself), if in practice client developers can't or won't implement it safely then we shouldn't bring it back from the dead. Peter