News for hackers. Stuff that matters.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by olavk on Friday April 13, 2018 @09:48AM (#16829931)
But the web already contains billions of pages which do not conform to XHTML. Any browser or scraper would still have to able to parse those to be of any use. Adding XHTML would just be an additional parser frontend, it would not simplify anything.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by kuschku on Friday April 13, 2018 @09:51AM (#16829955)
That’s not true – the WHATWG has already deprecated some HTML specs, and older HTML pages already break today.

XHTML would have worked the same way – after a few years, you can deprecate the old parsers.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by olavk on Friday April 13, 2018 @10:08AM (#16830099)
As far as I know, WHATWG have deprecated some elements not widely used (like "isindex", "font"), but the documents using these elements will still be readable even if not exactly as the author intended. Moving to XHTML, on the other hand, would make billions of pages totally inaccessible.

There are people who are now dead who have pages on the internet. These pages will never be updated.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by hsivonen on Friday April 13, 2018 @01:25PM (#16832022)
font still works. isindex does not. It's extremely rare for a cross-browser HTML element to get removed but isindex is one of those.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by kuschku on Friday April 13, 2018 @03:08PM (#16833021)
blink also doesn’t work anymore, and neither does marquee. Several of the frame attributes are broken as well. noscript doesn’t always work reliably depending on browser.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by hsivonen on Friday April 13, 2018 @03:24PM (#16833164)
Marquee works for me in Gecko and Blink. Didn't test the other two engines.