14 ms·
HTML 5.2 Recommendation
- TazeTSchnitzel 9y agoWHATWG needs to add a <w3c-please-stop-plagiarising-the-whatwg-html-standard /> tag then gate some useful functionality behind it to see if W3C will dare include it
- zaarn 9y agoFor the lazy and/or those unable find the link in the massively oversized index; [0] Changes listed here [0]: https://www.w3.org/TR/html52/changes.html#changes https://www.w3.org/TR/html52/changes.html#changes
- itsbits 9y agothght noreferrer value was already a standard.
- detaro 9y agoIt is. W3C HTML5 standards are merely following/copying what WHATWG and the browser makers are doing, with little actual relevance.
- pjmlp 9y agoThe relevance it that W3C HTML5 standards are supposed to already be stable everywhere, while WHATWG and the browser is a guessing game of what actually works and behaves the same way everywhere.
- detaro 9y agoI've never seen anyone reference it in that way, which doesn't mean nobody does, but was the basis for my wording of "little actual relevance". (Admittedly, going to either HTML spec is not something that's needed very often for most devs, since most changes happen in other specs (CSS, web platform APIs at W3C, ...) and/or are widely documented outside, but while I've had occasional discussions involving quotes from the WHATWG spec, W3C HTML5 spec hasn't been referenced at all) For the question "is this supported widely enough", caniuse.com + your local traffic stats is in most cases more relevant than inclusion in some spec or not.
- taspeotis 9y agohttps://www.w3.org/TR/html52/changes.html#changes https://www.w3.org/TR/html52/changes.html#changes
- igravious 9y agoTheir TOC needs to be collapsible and selectively expandable. UX fail imho.
- deleted 9y ago[deleted]
- vog 9y ago> Their TOC needs to be collapsible Not sure what you mean. In the lower left there is a working collapse button.
- igravious 9y agoNo, not the entire sidebar, the individual branch elements of the tree I mean. Like this: http://jsfiddle.net/tygrj1us/ http://jsfiddle.net/tygrj1us/
- planxty 9y agoThanks! All I want for Christmas is an obvious link in the top of every W3C document showing me what's new.
- rwmj 9y agoFor those who have not been paying attention for a decade, what's the relationship between this revision and WHATWG?
- igravious 9y agoIn the interests of completeness. “HTML Living Standard — Last Updated 13 December 2017” https://html.spec.whatwg.org/multipage/ https://html.spec.whatwg.org/multipage/ I've been telling students that the W3C develops and maintains the HTML spec. Looks like I'm dead wrong. Oops.
- kryptiskt 9y ago"Although we have asked them to stop doing so, the W3C also republishes some parts of this specification as separate documents."
- ChrisSD 9y ago> Copyright © 2017 WHATWG (Apple, Google, Mozilla, Microsoft). This work is licensed under a Creative Commons Attribution 4.0 International License. See https://creativecommons.org/licenses/by/4.0/ https://creativecommons.org/licenses/by/4.0/ > You are free to: > Share — copy and redistribute the material in any medium or format > Adapt — remix, transform, and build upon the material for any purpose, even commercially.
- oblio 9y agoI think the point here is not about the legality but more about the ethics of doing so, in this case.
- ChrisSD 9y agoIt just amuses me that they're effectively saying that anyone can fork this for any reason... except for the W3C.
- dragonwriter 9y agoNo, they are saying anyone is allowed to fork this for any reason, but we’d really prefer the W3C didn't fork this for the reason that they are, because it's confusing and counterproductive. Whether someone should be permitted to do something is a different issue than whether they should actually do it.
- scardine 9y agoIt is debatable if it is unethical given the license but it is definitely a disservice for the community.
- geofft 9y ago
- dmitriid 9y agoYeah. Only it's possibly WHATWG's proposal. Copied over with names changed and multiple errors here and there. See the full story here: https://www.reddit.com/r/javascript/comments/5swe9b/what_is_the_difference_between_the_w3c_and_the/ddkwft4/ https://www.reddit.com/r/javascript/comments/5swe9b/what_is_...
- magnat 9y agoWhat's the point of removing features such as "menu" from HTML standard? If there are browsers supporting it and webpages using it, would Mozilla (or Google or Microsoft) actually remove those features just because newest standard said so? I mean: marquee was deprecated long ago, yet browsers still render it correctly.
- deleted 9y ago[deleted]
- sureaboutthis 9y ago<marquee> has never been part of any HTML standard, ever. It is listed as an obsolete feature in the HTML5 standard for the point of making it obsolete (a weird reason) but not mentioned anywhere else since time began. I don't recall the reasons for removing <menu>
- geofft 9y ago<isindex> got removed from browsers, which I personally find kind of sad because that's what I learned in 1995 and I've written a web page that uses it. But it's weird and does nothing that a normal form couldn't do, so the browsers seem to want to deprecate it.
- domenicd 9y agoThe biggest weirdness about it was that it was essentially a parser macro, not an element. That is, at parse time, it expanded into a form/label/hr/input set of elements into the token stream. Super-bizzare. See the removal patch at https://github.com/whatwg/html/commit/5c44abc734eb483f9a7ec79da5844d2fe63d9c3b https://github.com/whatwg/html/commit/5c44abc734eb483f9a7ec7....
- kenbellows 9y agoI can't speak for the spec authors, but IMHO, tags should be deprecated and eventually removed when they are deemed to be useless, especially when their functions and/or semantics are covered by another tag, and especially when their use is harmful (or rather, more harmful than beneficial). In my (very personal) opinion, an HTML tag or attribute, and more generally a feature of any design/development framework, should be considered possibly harmful if it: - presents possible security problems; for examples, consider some of the points listed here: https://html5sec.org/ https://html5sec.org/ - promotes poor usability or accessibility; e.g. interactive tooltips with links or controls in them, for example, are quite difficult to make accessible, and I wouldn't want an HTML <tooltip> tag without a lot of discussion about accessibility - promotes anti-patterns; e.g., at this point I think <marquee>-style scrolling informational text is an anti-pattern in a web context, since it can the text much harder to read, especially on small screens Of course, none of these concerns should lead to immediate removal of a thing as soon as they're pointed out, but they should be discussed and considered. It's a cost-benefit analysis: what does this feature actually buy us that isn't easily achievable with other features, what problems is it causing and how severe are they, and are the benefits worth the problems? As for <menu>, my guess, though I haven't been able to find the actual discussion, is that it was removed because its semantics are somewhat in conflict with <nav>, and probably its most common use was custom context (aka "right-click") menus, which bring a lot of accessibility problems with them. I don't know that I agree with the decision to remove it altogether, since I think its use to semantically identify and group web application controls is very valuable and not covered by any other tags (though I'd love to be corrected), but I do think that context menus, which to me seems like the most common use for the <menu> tag, are a very problematic design element. Again, it's a balance; is it worth the problems it causes? I guess the authors decided it wasn't. (Just to reiterate, I don't know why <menu> was removed, I'm just guessing. If anyone can find any of the discussions about <menu> and the problems with it, I'd love to read more.)
- tobyhinloopen 9y agowhat's with the separation of w3c & whatwg? Are there now 2 HTML5-ish standards? Also, I thought HTML5 was going to be the "final version"
- jlebrech 9y agonope, html needs to stop. it's a document markup language and shouldn't be used for apps.
- jrochkind1 9y agogood luck with that.
- SimeVidas 9y agoWhat‘s the alternative (for web apps)?
- jlebrech 9y agodon't make them
- dbbk 9y agoNo one should make web apps? Good one.
- lewisflude 9y agoWhere would you draw the line between a "website" and a "web app", would you like to see JS die entirely? Would you like the web to be non-interactive. Genuinely interested.
- jlebrech 9y agointeractivity should move to a newer platform and the web should just be for brochure sites, articles and legacy stuff. there should be a new platform that uses a new engine that's isn't backwards compatible. It might be possible to do this soon with wasm+canvas, but then you have unused rendering engines (html/css) and it's recreated from the ground up.
- reificator 9y agoIs that a practical "should" or an ideological "should"?
- andrewmcwatters 9y agoI wish WHATWG would properly version their work. I don't like the idea of a "living standard" because it leads to checking for individual functionality and feature detection, rather than being able to say, "This is fully HTML 5.x.x compliant." Regardless of the state of W3C, if I built an embedded renderer based on their specs, I could at least say, "this renderer is based on <http-ref> and link to the recommended spec version. Whereas if I did that with the living standard href, I'd be out of date any time they decided to rename an attribute.
- geofft 9y agoBut that's the point - web authors are supposed to use feature detection instead of writing to a particular standard version. It turns out to be a better model for large interfaces. Yes, in theory, you can ask "Is this OS POSIX.1-2008-compliant or not." In practice, it takes a while to e fully POSIX.1-2008-compliant, and so you get autoconf, with its individual feature detections of specific function. Less clean, but way more practical. If you're writing an embedded renderer, you can always say "This is compliant with the standard as of 14 December 2017." If you're writing an embedded renderer that is being applied to the live web and not just to a fixed set of pages that are also embedded (e.g., you're shipping HTML documentation and a viewer, or a kiosk, or something), you will in fact be out-of-date when the living standard changes. There's no point in saying "I'm compatible with HTML 5.2.0" because the live web isn't targeting 5.2 any more. So you can either acknowledge that, or figure out how to get software updates.
- andrewmcwatters 9y agoGood point, thanks. I suppose that's just the nature of it.
- colanderman 9y agoHow does one perform feature detection in a static HTML page? As far as I can tell the only way to author a compatible web page these days is by checking every damn feature of HTML you use against some humongous table like Can I Use? before assuming your audiences' browsers support it. Compare to versioned specs, where I need simply determine the minimum spec version supported by my target audience (and any exceptions to the spec) and code against that spec. There is some utility in naming sets of well-supported features...
- bringtheaction 9y agoWasn't HTML 5 supposed to be the last explicit version and then it would be a living standard without changing the version number?
- toxicFork 9y agoHTML 2018.1 disagrees
- currysausage 9y ago"HTML", not "HTML 5", yes: https://html.spec.whatwg.org/multipage/ https://html.spec.whatwg.org/multipage/ The W3C regularly publishes forks [1] of the WHATWG HTML Living Standard. They have good SEO, but not much relevance. [1] http://lists.w3.org/Archives/Public/www-archive/2014Apr/0034.html http://lists.w3.org/Archives/Public/www-archive/2014Apr/0034...
- deleted 9y ago[deleted]
- dragonwriter 9y agoNo, WHATWG dropped numbers in favor of the “living standard”, but W3C continued to issue numbered HTML version standards.
- masswerk 9y agoHm – I'm not too happy to see most of the original HTML-elements marked "not conforming" and "must not be used", thus preparing for browsers to eventually drop the support. There are still lots of web-sites and valuable information stored and archived in this format. Back in the day, it was thought that basic HTML was a format to last. Who is going to update these documents in order to make them conforming to future browsers? Or are we just dropping a decade of documentation? Is it worth it? (Consider: Apparently, MS-Word docs or PDF prove longer lived than basic HTML documents! Who would have thought of this?)
- jraut 9y agoDropping the support does not make the elements non-functional. Instead, they are presented differently. Formats and notations do undergo changes. The comment mentions long-lived MS-Word doc. Which version of those, specifically, has been around the longest so far?
- masswerk 9y agoI'm really afraid that this is preparing the final drop of browser support. (We've seen similar in http, where many of the http/1.1 (1997) features, like multipart-http, for-headers, etc. aren't supported by any client for years by now.) As for MS-Word and HTML: When I finished my thesis in the mid-1990s, I saved it both in the MS-Word version, I used to write it (MS Word 5 for Mac), and HTML (expecting future compatibility). I can still open the Word version, but I may be soon unable to conjure a formatted display of the HTML-version. And I can still display a PDF 1.x...
- talmand 9y agoWhat do you mean by "browser support"? What functionality do you expect to go away that would prevent you from viewing an old HTML file in a modern browser?
- masswerk 9y agoE.g., drop of framesets. Many old documentations use them, as do most websites from the second half of the 1990s (so-called 2nd gen. websites). Without frames, the content can't displayed in context anymore and consistency of presentation is lost entirely.
- exabrial 9y agoI really wish we'd "simplify" the HTML spec. The "pave the cow paths" approach to allow non-closed tags and mix of various syntaxes has lead to an explosion of complexity. That has regressed into terrible performance and memory hungry parsers.
- rhencke 9y agoThis was done once - it was called XHTML. It was, effectively, just HTML in XML form. Tags had a single syntax (no implicitly self-closing tags). Documents were required to be well-formed, syntactically, or they would not display. It did not win.
- dragonwriter 9y agoIt also didn't lose, since WHATWG HTML retains an XML syntax (no longer formally called XHTML, But it's the evolution of the same thing.) There are still use cases for the XML syntax.
- tannhaeuser 9y agoHTML had tag omission and other minimization features from day one since HTML is based on SGML which formalizes these notions. If by mix of various syntaxes you mean CSS, then I have to agree with you. There never was a need to define a new syntax for item/value pairs; plain markup attributes were and are sufficient for presentation properties.
- _nalply 9y agoThis 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. Ah, hyperbole. I didn't know that humor could be specified.
- philipwhiuk 9y ago<link rel="humour" type="text/hyperbole" href="w3cHumour.hss" />
- yuhong 9y agoI already have suggested to base the W3C snapshots on the WHATWG web developer edition.
- tebruno99 9y agohere is an idea, how about the w3 go to hell after selling us out on DRM.