7 ms·
This is a completely irrelevant document. Browser makers follow standards written by the WHATWG (Web Hypertext Application Technology Working Group), not the
by bryanlarsen 10y ago
This is a completely irrelevant document. Browser makers follow standards written by the WHATWG (Web Hypertext Application Technology Working Group), not the W3C.
I'm horribly oversimplifying, but to see the full ugliness, just google 'whatwg w3c'
- Touche 10y agoThis. Anyone who reads this please flag this article as it confuses developers.
- roblabla 10y agoAny specific article explaining what the difference between the two are ? My google being in french, I don't get much results...
- okket 10y agoFurther down is a comment by LukeShu that explains the difference a bit: https://news.ycombinator.com/item?id=12849105 https://news.ycombinator.com/item?id=12849105
- domenicd 10y agoI tried to leave some details here on the situation downthread: https://news.ycombinator.com/item?id=12849375 https://news.ycombinator.com/item?id=12849375 As for actual technical differences, the vast majority of them are bugs introduced during the copying process, or just places where they haven't caught up to our bug fixes/new features/removals of unimplemented features. (Bug fixes especially roll in quite frequently; see https://github.com/whatwg/html/commits/master https://github.com/whatwg/html/commits/master .) There are some differences around conformance requirements, as some of the W3C HTML editors see their fork as a venue for writing a nice official-looking documenton how they think certain HTML elements should be semantically interpreted and used. The big ones I remember are around figcaption, main, hgroup, and others. My favorite is when they made it a high priority to change one of the examples not to use the Flying Spaghetti Monster since it might be controversial. This does not affect implementations of browsers though, just what conformance checkers (validators) like http://checker.html5.org/ http://checker.html5.org/ tell you about whether your document is conformant. You can get a full comparison via the third-party tool https://diffofhtmls.herokuapp.com/ https://diffofhtmls.herokuapp.com/.
- IshKebab 10y agoBasically W3C tries to define versioned HTML specifications, but they basically follow what browsers actually implement and are always out of date. WHATWG maintain a "living standard" and is really what browser vendors actually work with because it doesn't attempt the slow and futile task of defining a 'stable' versioned spec. Something like that anyway.
- positivecomment 10y agoYou already got many relevant answers but just in case you need it again, https://www.google.com/ncr https://www.google.com/ncr redirects to the international version.
- j_jochem 10y agoFor me, this redirects to the German version (I'm in Germany on a device with a German locale). I'd really love to have a way to tell Google to only show English-language hits.
- BBlarat 10y agoThat would be great, I'm living in Sweden and I prefer english hits as they're usually more relevant, unless I google something swedish that is.
- tauchunfall 10y agoJust append `&hl=en` to the URL. This should work. I've set my browser to English as default and use `&hl=de` to tell Google to mix some German hits into the query result.
- andrewmcwatters 10y ago> This is a completely irrelevant document. This is NOT true. W3C vs WHATWG is a "political" issue. Saying either group publishes completely irrelevant documents is misleading.
- domenicd 10y agoRight, everything is relevant to someone. But the grandparent was talking about what is relevant to browser vendors (and thus web developers), in which case it's pretty clear.
- andrewmcwatters 10y agoThere are developers who solely rely on W3C recommendations to implement renders, parsers, and other standards-conforming mechanisms, widely because they provide actual versioning rather than a living standard. How clear this is to actual implementors is a matter of debate and preference.
- Touche 10y agoCan you list some of these tools so that I can avoid using them, as they likely contain bugs that are fixed upstream in whatwg/html?
- kuschku 10y agoWHATWG is a bug. A set of browser vendors just choosing the maximum superset of their implementations for everything. Everything is compatible. That’s the worst possible way to define a standard. A standard is important because it sets limits of what is allowed and what not. Because it is more strict than anything that came before. Because you can actually just implement it, and if something doesn’t work, you can complain to whoever didn’t follow it. The A paper standards say "A ratio of 1 to sqrt(2), A0 is 1m², every smaller standard is exactly half the area of the previous one". Not "Well it’s kinda this or that or that", as WHATWG does. The fight where WHATWG was trying to redefine what URL means, and tried to force cURL and other projects to parse completely retarded patterns as "http:/google.com" (notice the typo) as URL is just another example. As I said in another comment, a standard is supposed to shape the environment it describes, make it simpler. WHATWG standards don’t fulfil that description, they make the web just more complicated than it already is.
- haikuginger 10y agoRather, the WHATWG writes standards that comply with what browser makers do.
- Manishearth 10y agoIt goes both ways. Unspecced behavior might get specced by the whatwg. Of it turns out that whatwg's spec doesn't match most browsers, that is a spec bug. If it matches some browsers but not others it usually gets discussed and consensus is reached. Sometimes the spec does one thing, some browsers do a different thing, and some browsers do yet another thing. More discussion. But new features like the fetch standard get written before implementations (with vendors and other stakeholders involved in the process), or simultaneously with implementations.