News for hackers. Stuff that matters.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by Sharlin on Friday April 13, 2018 @10:46AM (#16830439)
> Most of the web quickly moved to XHTML.

This simply is not true. The web moved to an XHTML-like dialect of HTML which was still served as text/html and browsers interpreted it as "HTML soup" because actually serving pages as application/xhtml+xml would have broken the majority of the web because browsers would actually validate them and refuse to display a page at all if there was even a single missing close tag.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by lucideer on Friday April 13, 2018 @11:38AM (#16830999)
> This simply is not true. The web moved to an XHTML-like dialect of HTML

You're thinking of XHTML 1.1 or XHTML 2. That "XHTML-dialect" that everyone switched to was called "XHTML 1.0", which allowed serving as either content type.

If you're choosing to nitpick about the fact that most sites published would not have worked if served as application/xhtml+xml, I'd invite you to do a survey of sites currently being served as valid HTML5. It's not even that easy to verify as the Nu validator version in use varies so much depending on where it's hosted (or if it's a local jar), and which iteration of the living standard it conforms to is always ambiguous. Have you tried reading the WHATWG spec diffs?

The burden on devs who might like to adhere to any kind of strict automated verification of spec. conformance is now out of the question. With XHTML, even if you were serving non-well-formed XML with a text/html content-type, at least your markup could be trivially checked for conformance by almost any XML parser to see why it's not well-formed. It was actually conceivably viable to put that check into build steps or CI.

Serving application/xhtml+xml was a nice to have, but anyone believing that serving XHTML as text/html had no value completely missed the point. At least now, years later, the mess we're stuck with should make it a little easier to see though.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by jerf on Friday April 13, 2018 @01:15PM (#16831925)
OK, so by lucideer's quirky definition of "XHTML", the vast majority of the web moved to XHTML. Based on the expansiveness of lucideer's definition, this appear to have encompassed web developers who probably weren't even aware they were writing "XHTML".

By the definition that most of us are using, which is that XHTML is complaint XHTML that could be rendered without error in browser's XHTML modes, to a first approximation nobody ever did it. Even today XHTML-levels of precision in HTML requires an awful lot of API support and very careful usage; doing it ten years ago was above almost everybody's skill level.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by lucideer on Friday April 13, 2018 @01:37PM (#16832135)
> by lucideer's quirky definition

Which also happens to be the definition the w3c xhtml 1.0 spec. You can choose to think that's quirky, please don't attribute it to me.

> definition that most of us are using, which is that XHTML is complaint XHTML that could be rendered without error in browser's XHTML modes

Which, again, is the definition used in the later w3c xhtml 1.1 & 2 specs, the former which wasn't widely used, the latter which was abandoned without being published at all.

If your issue with XHTML was that W3C were moving towards a direction you disagreed with, then you don't have an issue with the version of XHTML that was in popular use.

> XHTML-levels of precision in HTML requires an awful lot of API support and very careful usage

I'm not really sure where this view comes from. HTML validation is a lot more complex and difficult to achieve than XML well formedness, and HTML4/XHTML1 validation were both far simpler than modern HTML5 validation (the Nu validator is inordinately complex in comparison to the older DTD one). Furthermore, dev tools for ensuring XML well-formedness are far more readily available and integrated into most things even today, while HTML5 validation is such an obscure concept today I'm sure many devs don't even know it's a thing.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by ubernostrum on Friday April 13, 2018 @03:12PM (#16833058)
Which also happens to be the definition the w3c xhtml 1.0 spec. You can choose to think that's quirky, please don't attribute it to me.

Except that the number of people who actually implemented valid, well-formed, properly-served XHTML Strict -- of any version -- in compliance with all the relevant specifications is at best vanishingly tiny. XHTML Transitional was tag soup.

Your retort further up about many sites serving invalid HTML5 actually works against you, since HTML5 explicitly has a forgiving parsing model, while XHTML is explicitly "every error is a fatal error". If browsers had enforced the XHTML approach on every document using an XHTML DOCTYPE, we would have seen the death of XHTML much earlier.

This is why people say XHTML was never really adopted -- many people certainly put a "/>" to close their empty elements, and stuck an XML prolog and an XHTML DOCTYPE up at the top, but surveys like the infamous "XHTML 100" showed that next to nobody actually adopted XHTML in a manner compliant with the relevant standards.

And I say this as someone who, way back in the early 00's, was serving valid, well-formed XHTML as application/xhtml+xml. XHTML was a terrible approach, and the W3C process was dragging farther and farther from practicality at every revision (remember XHTML 2.0?).

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by fourthark on Friday April 13, 2018 @07:58PM (#16834945)
You're taking about the ease of validation. Everyone else is talked about the ease of writing.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by kuschku on Saturday April 14, 2018 @07:58AM (#16836950)
Oh, you mean like AMP, which now every major site supports, and which is even stricter than XHTML?
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by adamrezich on Saturday April 14, 2018 @05:39PM (#16839676)
Turns out, when there's financial incentive to use strict syntax, people will... guess that's all XHTML lacked...
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by Hello71 on Sunday April 15, 2018 @10:11AM (#16842676)
I mean... yeah? "there must be an actual benefit to do something that costs me development time = money". XHTML did not offer this.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by hsivonen on Friday April 13, 2018 @12:55PM (#16831744)
> If you're choosing to nitpick about the fact that most sites published would not have worked if served as application/xhtml+xml, I'd invite you to do a survey of sites currently being served as valid HTML5.

Completely different thing. XML processing and all reasoning based on the premise of XML processing are fiction when XHTML is served as text/html. The HTML parsing algorithm and tve rest of the processing requirements is not fiction when HTML is invalid.

(Why are we still talking about this in 2018. Sigh.)

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by wink on Friday April 13, 2018 @03:02PM (#16832974)
Because someone asked and it explains some of the history quite nicely.

FWIW, maybe I'm the 1% but I wrote valid XHTML 1.0 for a while, but also soon gave up :P

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by Semaphor on Friday April 13, 2018 @07:36PM (#16834853)
I did server side browser sniffing to give IE the version it understood (IIRC it couldn't handle well-formed XHTML served with the proper mime tag, not sure, it's been a while :D) while everything else got proper fully compliant XHTML. I'm pretty sure I used a code snippet from Anne van Kesteren who is also posting here ;)
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by xtian on Friday April 13, 2018 @10:59AM (#16830566)
And the versions of IE in use didn’t support application/xhtml+xml anyway so you would have to switch to text/html based on the user agent string.

It was never clear what the technical benefit of this was supposed to be. I only ever saw one site whose pages served double duty as an API and UI by serving styled XML. It seemed like a challenging approach to pull off well.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by spiralx on Monday April 16, 2018 @12:13PM (#16850066)
I wrote an XSL stylesheet that turned an HTML page into a pretty-printed and syntax highlighted display of its source code.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by duskwuff on Friday April 13, 2018 @03:02PM (#16832977)
The shoe web site skechers.com used to do this. With the removal of XSL support from browsers, though, it looks like it's now using some form of JS templating.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by chias on Friday April 13, 2018 @11:28AM (#16830883)
The Gentoo website / handbook does this.

Or rather, did this a few years ago when I was last messing around with Gentoo. It seems to be HTML now.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by Hello71 on Sunday April 15, 2018 @10:14AM (#16842687)
The Handbook was interesting in that it was one of the few sites that actually went with the XML + XSLT = XHTML route. Of course, nobody knows XSLT, and everyone hates XML, so it was dumped in favor of MediaWiki, which everyone still hates, but at least now mostly understands how to use. (although the same people that insisted we use XML+XSLT also insisted we use SMW, which is even worse... I gave up then, but I hear they're trying to undo SMW now.)
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by chias on Sunday April 15, 2018 @12:26PM (#16843339)
Interesting!

What's SMW? I'm not familiar with the term and searching for it isn't being particularly helpful.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by Hello71 on Tuesday April 17, 2018 @09:12AM (#16857915)
Semantic MediaWiki
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by coding123 on Friday April 13, 2018 @11:19AM (#16830783)
Oh I remember this period of time and damn this is true. I think about 80% of the pages on the web during a certain time period had that tramp-stamp of XHTML Validated button somewhere on the page.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by jopsen on Friday April 13, 2018 @11:38AM (#16831002)
Only the cool sites :)
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by riquito on Friday April 13, 2018 @11:55AM (#16831195)
And you couldn't use target="_blank" in anchors...
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by AgentME on Friday April 13, 2018 @08:25PM (#16835071)
I remember the fierce battle in my mind trying to judge whether I wanted a proper strict xhtml page, or I wanted external links to open in a separate window... This was literally what drove me away from strict xhtml. Everything else I was on board for at the time.