10 ms·
HTML 5.1 is a W3C Recommendation
- Osiris 10y agoIs there a document somewhere that summaries the proposed changes from HTML 5 to 5.1?
- piotrkubisa 10y agoI assume this document [1] may cover some changes. [1]: https://www.w3.org/TR/2016/REC-html51-20161101/changes.html#changes https://www.w3.org/TR/2016/REC-html51-20161101/changes.html#...
- 0x0 10y agoInteresting that "Having title, or writing email to a friend does not make an img missing alt conformant." What if you write an email to an enemy? https://www.w3.org/TR/2016/REC-html51-20161101/changes.html#changes-to-existing-features https://www.w3.org/TR/2016/REC-html51-20161101/changes.html#...
- rspeer 10y agoI found this table [1] that lists features specific to HTML 5.1 and their status in current versions of browsers. [1] https://w3c.github.io/test-results/html51/implementation-report.html https://w3c.github.io/test-results/html51/implementation-rep...
- myfonj 10y agoThere is also a diffed single page HTMLs at github [0], (11 MiB download; quite surprised my Firefox managed to render it). What I've found interesting is that markup for insertions and deletions in this file is ("non-semantic") `<span class="delete">..</span><span class="insert">..</span>`, instead of presumably more semantically appropriate `<del>..</del><ins>..</ins>` [1]. [0] https://github.com/w3c/html/blob/master/diff/html5to51diff.html https://github.com/w3c/html/blob/master/diff/html5to51diff.h... [1] https://www.w3.org/TR/2016/REC-html51-20161101/edits.html#elementdef-ins https://www.w3.org/TR/2016/REC-html51-20161101/edits.html#el...
- Chyzwar 10y agoNo, it is W3 having ass pain. HTML5 is living standard: https://wiki.whatwg.org/wiki/FAQ#When_will_HTML5_be_finished.3F https://wiki.whatwg.org/wiki/FAQ#When_will_HTML5_be_finished...
- sctb 10y agoReplying like this to a reasonable question is not the kind of civil discussion we ask for on HN.
- Chyzwar 10y agoThis is valid answer. This spec published by W3 have no practical value and only reflect some people political aspirations that were crushed when HTML5 won over XHTML2. In fact whole this W3 vs whatwg is harmful for the web. If W3 want to be useful they should either design new standard or contribute back to HTML5. Currently they hijack other people work and claim for their own. Expression I used "ass pain" is very clumsy translation of "ból dupy" and maybe better It would be to say butthurt.
- yuhong 10y agoI have been thinking of the "HTML5" buzzword and its problems for a while now.
- moron4hire 10y agoCare to elaborate? What specifically is wrong with HTML5? And how is it particularly worse than other offerings?
- yuhong 10y agoI am talking about the buzzword. For example, <canvas> dates back to 2005, long before the term was commonly used in the first place.
- moron4hire 10y agoAh, I see, clinging to inconsequential garbage.
- verandaguy 10y agoI don't really follow; your example's not clear. HTML5 is a standard, regardless of when the <canvas> element was first standardized, or even implemented. It's much less a buzzword than it is a set of specs which let HTML documents convey more semantic information, which in turns has implications for e.g. accessibility, among others.
- lucideer 10y agoI don't think this is what yuhong was referring to, but there's a lot wrong with HTML5. Googling "w3c whatwg", as one commenter suggested, won't give you any real insight into the mess, but it will hint at it. TL;DR The above document is irrelevant and should be ignored. Popular browsers' implementations define the HTML5 that most devs will want to target, and those browser vendors are members of the competing WHATWG body. They will largely ignore the W3C copy.
- yuhong 10y ago
- bryanlarsen 10y agoThis 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/.
- WoodenChair 10y agoFrom section 1.5: It must be admitted that many aspects of HTML appear at first glance to be nonsensical and inconsistent. HTML, its supporting DOM APIs, as well as many of its supporting technologies, have been developed over a period of several decades by a wide array of people with different priorities who, in many cases, did not know of each other’s existence. Features have thus arisen from many sources, and have not always been designed in especially consistent ways. Furthermore, because of the unique characteristics of the Web, implementation bugs have often become de-facto, and now de-jure, standards, as content is often unintentionally written in ways that rely on them before they can be fixed. That kind of says it all when it comes to web standards!
- Torgo 10y agoI think about this when I am using XMLHttpRequest in a web worker, and can't actually get an XML document back because you don't have access to an xml parser because there's no dom in web workers.
- andrewmcwatters 10y agoWhy would you use XMLHttpRequest in a web worker? Why would you not just delegate working with the result to a web worker? The requests shouldn't dispatch any faster.
- Torgo 10y agoonly point here is it was it was explicitly created for getting back an xml document (by microsoft, outside of any standards body, no less) while 99% of the time it's returning text or json, and in a web worker this XML tool literally can't return an XML document at all.
- gsnedders 10y agoIt can also fetch content over FTP in most browsers, in which case it isn't necessarily an HTTP tool either.
- wppick 10y ago> This specification should be read like all other specifications. First, it should be read cover-to-cover, multiple times. Then, it should be read backwards at least once. Then it should be read by picking random sections from the contents list and following all the cross-references. Not sure if this is serious. https://www.w3.org/TR/2016/REC-html51-20161101/introduction.html#how-to-read-this-specification https://www.w3.org/TR/2016/REC-html51-20161101/introduction....
- mstade 10y agoI don't think it is. It reminds me of something I've read before. I immediately thought of Hitchiker's Guide, but can't find the reference so it might not be. Still, I have a very distinct feeling I've read this before.
- Manishearth 10y agoIt's mostly an import of the whatwg spec, which gets whimsical at times. That is actually a pretty accurate representation of how reading entire specs with intent to implement goes. I've done this twice with the xhr and file specs :) Maybe not the reading backwards part.