News for hackers. Stuff that matters.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by anonymfus on Friday April 13, 2018 @10:05AM (#16830075)
>because it mandated error handling in ways that no browser implemented

IIRC Opera implemented XHTML error handling.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by kalleboo on Friday April 13, 2018 @10:43AM (#16830403)
IIRC several major browsers implemented XHTML error handling, but only for documents with a Content-Type: application/xhtml+xml header, which was basically nothing because that would then trip up other browsers
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by rimliu on Friday April 13, 2018 @10:48AM (#16830461)
Opera had the "draconical" approach, where upon the error you just had that, an error. Firefox, iirc had a softer approach where you still got the page rendered, but you'd get the error reported too. Anyway it all depended on the proper MIME type for the XTHML (as it should). However the whole MIME type and everything associated with it (some elements and APIs are treated differently) is a whole barrel of worms, so XHTML in any of the incarnations was never a good idea.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by winkeltripel on Friday April 13, 2018 @11:02AM (#16830602)
> "draconical"

That's xml error handling, following rules as written.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by tptacek on Friday April 13, 2018 @11:08AM (#16830655)
"Draconian" error handling is a term of art in HTML.