News for hackers. Stuff that matters.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by bzbarsky on Friday April 13, 2018 @11:42AM (#16831058)
The only reason there is a URL standard in the WHATWG is that the IETF URL RFC didn't define error handling and this led to interop problems. So there was a need for a URL standard that _would_ define error handling. The IETF refused to produce one (basically said "fuck you, we don't care about your use cases or interop problems" with slightly more polite wording), so the WHATWG ended up doing it...

I'm not saying this is a great situation. I'm not saying the WHATWG couldn't try to do better at considering non-HTTP or non-browser use cases here. But the representatives of those use cases in the IETF told browsers to take a hike. And then browsers did.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by kuschku on Saturday April 14, 2018 @08:01AM (#16836959)
The first line of the WHATWG URL spec says that it deprecates and replaces all IETF URL standards.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by bzbarsky on Wednesday April 18, 2018 @10:42PM (#16872952)
For its target audience (browsers and web pages) it does.